Hello all,
The presentation is delayed as it is so big it needs approval by the list master. Sorry about that.
Robert
2008/6/1 Robert Virding rvirding@gmail.com:
The LFE presentation.
Robert
Is there a permanent link to it? That might be easier and better than trying to fit it into the list.
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] There is no such thing as philosophy-free science; there is only science whose philosophical baggage is taken on board without examination. -- Daniel Dennett, Darwin's Dangerous Idea
2008/6/2 Robert Virding rvirding@gmail.com:
Hello all,
The presentation is delayed as it is so big it needs approval by the list master. Sorry about that.
Robert
2008/6/1 Robert Virding rvirding@gmail.com:
The LFE presentation.
Robert
erlang-in-lisp-devel mailing list erlang-in-lisp-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/erlang-in-lisp-devel
OK, there is one now:
http://forum.trapexit.org/viewtopic.php?p=43941#43941
2008/6/3 Faré fahree@gmail.com:
Is there a permanent link to it? That might be easier and better than trying to fit it into the list.
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] There is no such thing as philosophy-free science; there is only science whose philosophical baggage is taken on board without examination. -- Daniel Dennett, Darwin's Dangerous Idea
2008/6/2 Robert Virding rvirding@gmail.com:
Hello all,
The presentation is delayed as it is so big it needs approval by the list master. Sorry about that.
Robert
2008/6/1 Robert Virding rvirding@gmail.com:
The LFE presentation.
Robert
erlang-in-lisp-devel mailing list erlang-in-lisp-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/erlang-in-lisp-devel
Nice presentation. Thanks a lot!
Silly remarks: * in CL, bitvectors\ are like that: #*01110111 http://arti.vub.ac.be/docs/HyperSpec/Body/02_dhd.htm I don't know whether they correspond to Erlang binary constants, but if they do, you may keep the same syntax (or not since CL ones are actually writeable). * instead of fletrec you might or not want to use labels. Now your lisp dialect will by definition be incompatible with any other dialect, so it probably doesn't matter too much. * for gensyms that work across upgrade of distributed code, if you're afraid of collisions, you might consider prepending the gensym'ed symbol name with the crypto hash of the module code being compiled.
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Dost thou love life? Then do not squander time, for that's the stuff life is made of. -- Benjamin Franklin
2008/6/2 Robert Virding rvirding@gmail.com:
OK, there is one now:
http://forum.trapexit.org/viewtopic.php?p=43941#43941
2008/6/3 Faré fahree@gmail.com:
Is there a permanent link to it? That might be easier and better than trying to fit it into the list.
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] There is no such thing as philosophy-free science; there is only science whose philosophical baggage is taken on board without examination. -- Daniel Dennett, Darwin's Dangerous Idea
2008/6/2 Robert Virding rvirding@gmail.com:
Hello all,
The presentation is delayed as it is so big it needs approval by the list master. Sorry about that.
Robert
2008/6/1 Robert Virding rvirding@gmail.com:
The LFE presentation.
Robert
erlang-in-lisp-devel mailing list erlang-in-lisp-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/erlang-in-lisp-devel
2008/6/4 Faré fahree@gmail.com:
Nice presentation. Thanks a lot!
Thank you, thank you.
Silly remarks:
- in CL, bitvectors\ are like that: #*01110111 http://arti.vub.ac.be/docs/HyperSpec/Body/02_dhd.htm
I don't know whether they correspond to Erlang binary constants, but if they do, you may keep the same syntax (or not since CL ones are actually writeable).
In a sense I think they are the same. The main problem with using the CL bitvector syntax is that binaries are usually much bigger, sometimes mega-bytes.
- instead of fletrec you might or not want to use labels. Now your
lisp dialect will by definition be incompatible with any other dialect, so it probably doesn't matter too much.
I don't like the labels name and I am free to do as I want. :-) At least until we are more people working on LFE, if that ever occurs.
- for gensyms that work across upgrade of distributed code, if you're
afraid of collisions, you might consider prepending the gensym'ed symbol name with the crypto hash of the module code being compiled.
That would work, but I don't really know how worried I am about the problem. It was more a comment on that neither Scheme's hygiene and gensym are really safe unless you use them as intended. We'll see what the users need.
Robert
erlang-in-lisp-devel@common-lisp.net
-
Faré -
Robert Virding