Re: Nyacc question: where are the actions bound?

[Matt Wette <matt.wette@gmail.com>]

On 3/8/20 3:14 AM, tomas@tuxteam.de wrote:
> Hi,
>
> I'm playing around with Nyacc: I found a first little use case
> to get my feet wet.
>
> First of all, than you, Matt, for this impressive package.
>
> Shamelessly stolen from the minimal example, playground looks
> roughly like this:
>
> #+begin_source scheme
>    (use-modules (nyacc lalr))
>    (use-modules (nyacc lex))
>    (use-modules (nyacc parse))
>    
>    ;; to be used in some ($$ ...) actions:
>    (define (collect arg) (display arg))
>    
>    (define my-grammar
>      (lalr-spec
>       (start my-file)
>       (grammar
>        (my-file
>         (elt-list))
>        ;; more productions, calling out to ($$... collect)
>        (name
>         ($ident)))))
>    
>    (define mach (make-lalr-machine aq-grammar))
>    (define mtab (lalr-match-table mach))
>    (define gen-lexer (make-lexer-generator mtab))
>    (define raw-parse (make-lalr-parser mach))
>    (define (parse) (raw-parse (gen-lexer)))
>    (parse)
> #+end_source
>
> So I defined some function =collect= which will be called from
> actions in the grammar.
>
> My question is: where is the stuff resolved which is mentioned
> in grammar actions? My first experiments indicate that it's
> looked up at (module) top level, as if (grammar ...) greedily
> weaved that in at compile time.
>
> My idea would be to (pre-) define a grammar and to exchange
> the actions later as needed. Or would I have to re-define the
> grammar whenever I change my mind about actions?
>
> Note that I'm still very much in exploratory mode: "you're
> holding it wrong" would be a perfectly adequate answer, as
> would be "your mumblings are pretty unintelligible" :-)
>
> Cheers & thanks
> -- tomás
Nyacc was envisioned with the paradigm you propose, by using tags.
But I have not tried that in a while.  If you look at the example calc
in examples/nyacc/lang/calc/mach.scm you will see

(define (gen-calc-files)
   (write-lalr-actions
    full-mach "mach.d/calc-full-act.scm" #:prefix "calc-full-")
   (write-lalr-tables
    full-mach "mach.d/calc-full-tab.scm" #:prefix "calc-full-")
   (write-lalr-actions
    stmt-mach "mach.d/calc-stmt-act.scm" #:prefix "calc-stmt-")
   (write-lalr-tables
    stmt-mach "mach.d/calc-stmt-tab.scm" #:prefix "calc-stmt-")
   )

You can run this, then you can use the generated files to provide
the parser (don't need to run make-lalr-machine anymore.  There
are two files generated: one with all the parser tables and one
with the actions (only).   You could (copy and) modify the actions
file to get different parser actions.   That file includes comments
to help:

(define calc-full-act-v
   (vector
    ;; $start => prog
    (lambda ($1 . $rest) $1)
    ;; prog => stmt-list
    (lambda ($1 . $rest) (tl->list $1))
    ;; stmt-list => stmt
    (lambda ($1 . $rest) (make-tl 'stmt-list $1))
    ;; stmt-list => stmt-list stmt
    (lambda ($2 $1 . $rest) (tl-append $1 $2))
    ;; stmt => "\n"
    (lambda ($1 . $rest) `(empty-stmt))
    ...

Hope this helps.

Matt