From: Andy Wingo <wingo@pobox.com>
To: Phil <theseaisinhere@gmail.com>
Cc: Michael Lucy <MichaelGLucy@gmail.com>, guile-devel@gnu.org
Subject: Re: PEG Parser Updates/Questions
Date: Mon, 30 Aug 2010 08:32:53 -0700 [thread overview]
Message-ID: <m3iq2sxgii.fsf@unquote.localdomain> (raw)
In-Reply-To: <AANLkTim-ihMKThRgVo8bpV9YxxjyBh08D6L9=fEPzgp8@mail.gmail.com> (Phil's message of "Sun, 29 Aug 2010 02:45:19 -0500")
Hi,
On Sun 29 Aug 2010 00:45, Phil <theseaisinhere@gmail.com> writes:
> So is there a sort of ETA on when [PEG and other SoC projecsts] will
> be part of Guile?
Mmm, not really. I hope it will be soon, but I want to go through the
code patch-by-patch, and that will take at least 3 or 4 hours, if
everything goes well -- if there are problems it could take longer...
So I don't want to make myself look silly again by mentioning a date :)
Cheers,
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2010-08-30 15:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 5:13 PEG Parser Updates/Questions Michael Lucy
2010-07-28 5:41 ` No Itisnt
2010-07-28 5:51 ` Michael Lucy
2010-08-06 6:40 ` Michael Lucy
2010-08-16 5:37 ` Michael Lucy
2010-08-20 21:30 ` Andy Wingo
2010-08-29 7:45 ` Phil
2010-08-30 15:32 ` Andy Wingo [this message]
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=m3iq2sxgii.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=MichaelGLucy@gmail.com \
--cc=guile-devel@gnu.org \
--cc=theseaisinhere@gmail.com \
/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).