Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Class::Immutable and Abusing ORMs 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • The Erlang language is also based around the fact that after you give a variable some value, you can't change it back. You can invoce your function again with a new calulated value for example.

    They do that because it avoids problems with side-efects and action at a distance.

    I've been learning Erlang and I must say, I like it a lot, and I hope that the concurrency model of Perl6 will borrow some stuff from them.

    --
    life is short

    • Variables in Erlang are "Single Assignment", but this is not only for avoiding of side-effects but also because by never allowing the mutation of a variable the compiler can make lots of assumptions off of which it can make lots of optimizations (the wikipedia [wikipedia.org] page on the subject is pretty decent actually).

      There is actually a single assignment C dialect [sac-home.org], a single assignment Java dialect [wikipedia.org] and if you dig, I bet you can find one for FORTRAN too.

      - Stevan

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.