From: <tomas@tuxteam.de>
To: Guile User <guile-user@gnu.org>
Subject: Nyacc: how to lex comments?
Date: Mon, 16 Mar 2020 22:39:41 +0100 [thread overview]
Message-ID: <20200316213941.GA5467@tuxteam.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1650 bytes --]
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
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2020-03-16 21:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 21:39 tomas [this message]
2020-03-17 0:11 ` Nyacc: how to lex comments? Matt Wette
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=20200316213941.GA5467@tuxteam.de \
--to=tomas@tuxteam.de \
--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).