From: <tomas@tuxteam.de>
To: guile-user@gnu.org
Subject: NYACC: getting source location info?
Date: Fri, 10 Jul 2020 22:37:43 +0200 [thread overview]
Message-ID: <20200710203743.GA10781@tuxteam.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 489 bytes --]
Hi,
I'm having some fun with NYACC (thanks, Matt!).
To help debugging things and for errors and warnings, it'd be nice
to "know" where the current LHS non-terminal starts in the source.
Its endpoint is (is it?) (port-line (current-input-port) [and, of
course, (port-column ...)] -- at least some playing around suggest
that (and it makes sense, somehow).
Is there anything I've overlooked? Or do I have to hack the (or
roll-my-own) lexer for that?
Thanks for any insight
cheers
-- t
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2020-07-10 20:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 20:37 tomas [this message]
2020-07-11 3:00 ` NYACC: getting source location info? Matt Wette
2020-07-11 8:10 ` 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=20200710203743.GA10781@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).