Re: [elpa] externals/parser-generator 4d3830d8bd 1/4: Added error-handling for LR-SDT and improved parser generation replacing (nth) to (aref) when printing lambdas

[Stefan Monnier]

> I understand, it does not sound very Lispy, the Lispy idea that everything
> is supposed to be data objects, even code, but maybe (lambdas) is just an
> exception to this?

You're misunderstanding my question.  I'm fine with manipulating
functions as objects (as a matter of fact I'm a big fan).
Sadly, writing functions to a file to read them back in in another Emacs
session comes with various caveats.  Hence my questions:

    Where do these functions come from (where are they produced, how are
    they used until the moment you try to write them to a file)?
    Can you arrange to keep them as sexps/strings rather than as
    functions (until the time they're written to file), so the problem
    doesn't appear at all?

> (defvar
>   cvj-lex-analyzer--get-function
>   '#[(abc def) ((concat \"return %S\" abc def)) nil])
>
> (message "Output: %S"
>          (funcall 'cvj-lex-analyzer--get-function
>                   "first" "second"))

Remove that quote in front of `cvj-lex-analyzer--get-function`.


        Stefan