Re: eval use ?

Majorinc, Kazimir <false@xxxxxxxxx> writes:

How do you think "code=data" can be possible without EVAL?

Macros and closures.

Macros fall short here, because code=data means that code can
be processed during runtime

Macros can be compiled at runtime and the result used like any
previously compiled function or macro.


, just like data is usually processed during runtime.

The overwhelming impression is that you do not understand what is
going on either with eval or macros.


/Jon

--
'j' - a n t h o n y at romeo/charley/november com
.

Relevant Pages

  • Re: eval use ?
    ... Macros and closures. ... previously compiled function or macro. ... Its because you're plain stupido and you do not have a clue ...
    (comp.lang.lisp)
  • Re: The power difference between a macro and a function
    ... What extra expressive power macros give ... What's the point of being a programmer if you can't do these mechanical ... increased power lies with the language designer, ...
    (comp.lang.lisp)
  • CLAZY: lazy calling in Common Lisp
    ... In a bout of Haskell envy I did a few tricks with macros, closures and ... SYMBOL-MACROLET and added true lazy calling to CL. ...
    (comp.lang.lisp)
  • Re: eval use ?
    ... Majorinc wrote: ... Macros fall short here, because code=data means that code can be processed during runtime, just like data is usually processed during runtime. ... Closures are another form of code=data, in the sense that closure can be passed around as first-class values. ...
    (comp.lang.lisp)
  • Re: in macro from ANSI Common Lisp
    ... (defmacro in (obj &rest choices) ... (dolist (clos closures NIL) ... (defmacro in (obj &rest expressions) ... Well, once you introduce macros to implement syntactic abstractions, ...
    (comp.lang.lisp)