Erlang Development Environment

[Sean Hinde]

Andi,

> On Mon, Mar 05, 2001 at 04:25:15PM -0000, Sean Hinde wrote:
> > I've read a number of suggestions for a better Erlang Development
> > Environment than emacs.. It certainly seems we are falling 
> behind some other
> > languages in terms of support environment. (OCaml, Clean, 
> Python etc).
> 
> Could you describe what you think is wrong with the emacs 
> environment ? 

It's fine - I use it all the time. It is not everyone's cup of tea though -
other people here refuse to go near it and prefer to use vi, or notepad or
Joe or whatever If there was a nice dedicated environment which provided
integrated (meaning gui) support for some of the things I mentioned then I
believe that our Erlang experience would be a more pleasant and productive
one.

More seriously I am always in favour of providing the best tools to support
the people doing the job at the sharp end (which is why we are using Erlang
in the first place :-) ). Yes emacs can be made to do many things but when I
compare ease of use and accessibility between that and a nice gui clickware
environment with online help, automatic function name completion, Hit f1 to
get a reminder of the order of parameters for this library function...)
there is no real comparison.

Some people would continue to use emacs - others (including me, and I
suggest the majority of newcomers to the language) would use a dedicated
environment if there was one and it was any good.

> I think you're trying to reinvent the wheel ;) 

Absolutely right. There is nothing new here except that Erlang is in the
middle not Java, or C++, or Clean, or C#.

> > NOTICE AND DISCLAIMER:
> > This email (including attachments) is confidential.  If you 
> have received
> 
> Interesting.

Bizarre standard corporateware nonsense out of my control, please destroy
all e-mails from me before reading them otherwise you will be disobeying the
instructions which come after the body of the e-mail eh?

- Sean



NOTICE AND DISCLAIMER:
This email (including attachments) is confidential.  If you have received
this email in error please notify the sender immediately and delete this
email from your system without copying or disseminating it or placing any
reliance upon its contents.  We cannot accept liability for any breaches of
confidence arising through use of email.  Any opinions expressed in this
email (including attachments) are those of the author and do not necessarily
reflect our opinions.  We will not accept responsibility for any commitments
made by our employees outside the scope of our business.  We do not warrant
the accuracy or completeness of such information.