Tue Jul 22 10:48:50 CEST 2003
On Mon, 21 Jul 2003 erlang@REDACTED wrote:
> Here's a deeper question I would like to ask:
> How do you go about deciding which things are bad practice for erlang
> programmers which need complaints? The reason I ask is that there are
> neverending discussions of lint for C and why one should do what it
> says (or at least understand it) and why that constitutes good
> practice, however I have yet to see such a discussion in erlang.
I suppose that the situation is different with C, because it is a rather
low-level systems programming language ("glorified assembler" as some
would have it), and programmers need to be able to bend the language
into whichever shape they want it in order to make the code fast enough
or small enough for their particular purposes and hardware. Since
everybody needs to bend the rules in their own special way, there can be
no real consensus as to what the compiler should warn you about. In a
language like Erlang, the range of possible tricks that can go horribly
wrong is just so much smaller.
Richard Carlsson (richardc@REDACTED) (This space intentionally left blank.)
E-mail: Richard.Carlsson@REDACTED WWW: http://user.it.uu.se/~richardc/
"Having users is like optimization: the wise course is to delay it."
-- Paul Graham
More information about the erlang-questions