>>2
symta documentation or fuck off
symta documentation or fuck off
symta documentation or fuck off
symta documentation or fuck off
symta documentation or fuck off
symta documentation or fuck off
symta documentation or fuck off
symta documentation or fuck off
symta documentation or fuck off
symta documentation or fuck off
symta documentation or fuck off
symta documentation or fuck off
symta documentation or fuck off
symta documentation or fuck off
symta documentation or fuck off
symta documentation or fuck off
symta documentation or fuck off
symta documentation or fuck off
symta documentation or fuck off
symta documentation or fuck off
symta documentation or fuck off
Fexprs/first class macros are terrible. They can't do anything useful that isn't possible with regular macros. But they make local reasoning about code and compiling code hard.
Name:
2012-11-13 3:38
Name:
Anonymous2012-11-13 4:00
>>14
Not every Lisp needs to be compiled to machine code. A lot of Lisp are perfectly fine as interpreters for 90% of their use cases. Use C for the heavy lifting.
>>16 Not every Lisp needs to be compiled to machine code. A lot of Lisp are perfectly fine as interpreters for 90% of their use cases. Use C for the heavy lifting.
Lisp is supposed to be everything.
Name:
Anonymous2012-11-19 2:46
I'm split between Matt Might's mighty discovery and Kernel's oddball $vau crap, can anyone help?
Name:
Anonymous2012-11-19 3:00
But they make local reasoning about code and compiling code hard.
Factor has first class macros, and it doesn't have those problems.
Name:
Anonymous2012-11-19 3:14
>>19
You need to become insane in order to grok the latter. It's really not as bad as it sounds, and it's totally worth it.
Name:
Anonymous2012-11-19 10:37
>>19
It's basically fexprs, which is what macros are in newLISP
Name:
Anonymous2012-11-19 10:46
>>19
Aren't they equivalent? The same way that there are many different bases to a vector space, perhaps there are many constructs that allow first-class access to the environment and macros. Maybe Matt's mighty macros, plus lambda calculus, are exactly as powerful as $vau and wrap.
Name:
Anonymous2012-11-19 12:31
Name:
Anonymous2012-11-19 14:07
Name:
Anonymous2012-11-20 7:34
Name:
Anonymous2012-11-20 13:44
Name:
Anonymous2012-11-20 16:10
Name:
Anonymous2012-11-20 22:08
Name:
Anonymous2012-11-21 2:22
Name:
Anonymous2012-11-21 15:01
Name:
Anonymous2012-11-21 23:55
Name:
Anonymous2012-11-22 1:38
It seems to me as if Matt's macro construct is less disgusting and intrusive than Kernel's $vau. Since it doesn't manually manipulate the lexical environment of the ``caller'', it's probably easier to optimize (and reason about).
Name:
Anonymous2012-11-22 10:13
Name:
Anonymous2012-11-22 22:41
Name:
Anonymous2012-11-23 19:49
Fuck, this is driving me insane. $vau + wrap are ugly as fuck, yet Matt's macro construct doesn't seem to have first-class environments per se. Fuck.