Why Erlang is the best concurrent language available
Thu Jan 23 17:28:15 CET 2003
I agree with all comments made about why Erlang is so good. Learning erlang
after programming in C, C++ and Java was pure joy. I loved it so much, I
vowed that I wouldn't leave Ericsson until I found a job where I could use
Now it feels like I'm paid to have fun :)
That aside, xref does all that you want and more.
see how you can integrate xref into your build process.
From: Eric Newhuis [mailto:]
Sent: 23 January 2003 16:02
Subject: Re: Why Erlang is the best concurrent language available
1. Within a module I want strict explicit import rules. I want the compiler
to bark if I use a module that I haven't explicity imported. If not the
compiler then some sort of tool I can invoke from make.
2. Among interdependent modules I want something to check that all modules
actually exist before I run my code. I need something I can invoke from
I think these are the two things that are holding us up from claiming that
Erlang is ideal as Erlang can be. So once we figure out how to do these
things we'll be very happy and convinced.
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.
More information about the erlang-questions