From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: Bison-like source locations in LALR-parser
Date: Mon, 11 Aug 2014 20:21:39 +0200 [thread overview]
Message-ID: <878umusx8s.fsf@gnu.org> (raw)
In-Reply-To: 1406966311-19014-1-git-send-email-janneke@gnu.org
Hi, Jan,
Jan Nieuwenhuizen <janneke@gnu.org> skribis:
> I am using these patches to provide Bison-like source locations that we
> need for error messages and the like. The output of the parser is a
> plain scheme tree, now transparently annotated with source locations
> that match the parsed input file.
I don’t think this is needed. Lexers are expected to use
‘make-lexical-token’ and ‘make-source-location’ from (system base lalr)
to preserve source location information.
Besides, note that lalr.upstream.scm is a copy of the upstream lalr-scm,
hosted at <http://code.google.com/p/lalr-scm/>.
HTH,
Ludo’.
next prev parent reply other threads:[~2014-08-11 18:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-02 7:58 Bison-like source locations in LALR-parser Jan Nieuwenhuizen
2014-08-02 7:58 ` [PATCH 1/2] LALR-parser: provide bison-like location constructs @1 ... @n Jan Nieuwenhuizen
2014-08-02 7:58 ` [PATCH 2/2] LALR-parser: transparent source locations using source-proprerties Jan Nieuwenhuizen
2014-08-11 18:21 ` Ludovic Courtès [this message]
2014-08-13 19:53 ` Bison-like source locations in LALR-parser Jan Nieuwenhuizen
2014-08-13 21:01 ` Ludovic Courtès
2014-10-05 10:27 ` Bison-like source locations in LALR-parser -- upstream update Jan Nieuwenhuizen
2014-12-02 20:27 ` Ludovic Courtès
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=878umusx8s.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@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).