unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Matt Wette <matt.wette@gmail.com>
To: guile-user@gnu.org
Subject: Re: Nyacc: how to lex comments?
Date: Mon, 16 Mar 2020 17:11:59 -0700	[thread overview]
Message-ID: <b225fc61-c22a-d77f-b0d9-07df75ba2414@gmail.com> (raw)
In-Reply-To: <20200316213941.GA5467@tuxteam.de>

On 3/16/20 2:39 PM, tomas@tuxteam.de wrote:
> Hi,
>
> in my quest to play parsing, I'm failing when I try to cope with
> comments.
>
> Here's an excerpt from my current file
>
>      (define my-grammar
>        (lalr-spec
>         (start my-file)
>         (grammar
>          ;; boring grammar details elided
>             )))
>      
>      (define mach (make-lalr-machine aq-grammar))
>      (define mtab (lalr-match-table mach))
>      (define gen-lexer (make-lexer-generator mtab
>                         #:comm-reader (make-comm-reader '(("#" . "\n")))))
>      (define raw-parse (make-lalr-parser mach))
>      (define (parse) (raw-parse (gen-lexer)))
>      
>      ;; (gen-lexer)
>      (parse)
>
> Comments are shell-like, from "#" to end of line. Grammar
> works fine so-far, but when (parse) sees a hash-comment
> (even just a one-line input
>
>    # this is a comment
>
> it panics:
>
>      Backtrace:
>      In ice-9/boot-9.scm:
>        1736:10  6 (with-exception-handler _ _ #:unwind? _ # _)
>      In unknown file:
>                 5 (apply-smob/0 #<thunk 557754319740>)
>      In ice-9/boot-9.scm:
>          718:2  4 (call-with-prompt ("prompt") #<procedure 5577543308e0 …> …)
>      In ice-9/eval.scm:
>          619:8  3 (_ #(#(#<directory (guile-user) 5577543c1f00>)))
>      In ice-9/boot-9.scm:
>         2806:4  2 (save-module-excursion #<procedure 5577543b31b0 at ice-…>)
>        4351:12  1 (_)
>      In nyacc/parse.scm:
>           78:4  0 (_ _ #:debug _)
>      
>      nyacc/parse.scm:78:4: Throw to key `nyacc-error' with args `("~A:~A: parse failed at state ~A, on input ~S" "(unknown)" 1 0 " a comment")'.
>
> I feel I'm doing something stupid. What can I do to understand
> what's going on?
>
> Thanks & cheers
> -- tomás
>
>
make-comm-reader will not eat newlines at end of comment by default.
If you want the comment # ... \n to include the newline try adding 
#:eat-newline #t.

Matt




  reply	other threads:[~2020-03-17  0:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-16 21:39 Nyacc: how to lex comments? tomas
2020-03-17  0:11 ` Matt Wette [this message]
2020-03-17  7:46   ` tomas
2020-03-17 12:31     ` Matt Wette
2020-03-17 12:42       ` tomas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b225fc61-c22a-d77f-b0d9-07df75ba2414@gmail.com \
    --to=matt.wette@gmail.com \
    --cc=guile-user@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).