From: Chris Vine <vine35792468@gmail.com>
To: guile-user@gnu.org
Subject: Re: guile parser
Date: Wed, 13 Dec 2017 15:19:10 +0000 [thread overview]
Message-ID: <20171213151910.4ac4cbee@bother.homenet> (raw)
In-Reply-To: <20171213140718.00737b08@bother.homenet>
On Wed, 13 Dec 2017 14:07:18 +0000
Chris Vine <vine.chris@gmail.com> wrote:
> Hi,
>
> The documentation for the LALR parser provided as part of guile in the
> (system base lalr) module, formerly at
> https://code.google.com/archive/p/lalr-scm/, is now unavailable with
> the closure of google code.
>
> Does anyone know of an alternative location for the documentation?
Found it here: https://github.com/schemeway/lalr-scm/wiki
It looks as if the URL in the guile manual needs updating.
Chris
next prev parent reply other threads:[~2017-12-13 15:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 14:07 guile parser Chris Vine
2017-12-13 15:19 ` Chris Vine [this message]
2017-12-14 9:19 ` 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=20171213151910.4ac4cbee@bother.homenet \
--to=vine35792468@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).