Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon.

Pages: 1-

LispWorks

Name: Anonymous 2014-09-29 16:57

Name: Anonymous 2014-09-29 17:02

Lisp's dead, baby. Lisp's dead.

Name: Anonymous 2014-09-29 18:24

>>2
Can I have his motorcycle?

Name: Anonymous 2014-09-30 16:45

Lisp codewalking requires using compiler-specific implementation-dependent codewalkers to be robust.

http://christophe.rhodes.io/notes/blog/posts/2014/naive_vs_proper_code-walking/

Name: Anonymous 2014-09-30 16:56

>>4
Yeah, just use macrolet.

Name: Anonymous 2014-09-30 18:54

I suddenly felt very sad while reading the linked post.

Name: Anonymous 2014-09-30 19:12

>>4
I don't understand the problem. What do they mean by code walking?

Name: >>7 2014-09-30 20:32

I should have read the whole thing before responding. To implement that well you need a framework that allows macros to be aware of each other when they should interact. When it walks the interior code it could look for handlers in a table. When defining new macros, add appropriate handlers to the table.

>>6
Sometimes you can't escape complexity. But at least writing that macro in lisp is possible.

Don't change these.
Name: Email:
Entire Thread Thread List