From: steve@quintile.net (Steve Simon)
Subject: [9fans] all you yacc experts
Date: Sun, 13 Nov 2011 10:08:53 +0000 [thread overview]
Message-ID: <bce6ef9f641b86ae4aeb8bccc1daece5@quintile.net> (raw)
In-Reply-To: <e3fc34c33bb9592c91efed2675cd186f@proxima.alt.za>
Perhaps I'am way off base but surely the neatest solution would be to
modify yacc to produce a nice clean message format, modify the gc
to use that format.
The reason for not using just the same format blindly is it was designed
with the structure of gc in mind rather than a clean output format.
Who knows, by delving into yacc perhaps more or even better error
status can be extracted.
Then we just need to convince russ/the go authors to include plan9's yacc
as part of the go distribution, it wouldn't be unprecendented as go already
includes 8c, 8l and friends.
-Steve
next prev parent reply other threads:[~2011-11-13 10:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 16:07 ron minnich
2011-11-11 17:16 ` Steve Simon
2011-11-11 20:54 ` Bakul Shah
2011-11-11 20:58 ` ron minnich
2011-11-11 21:30 ` Bakul Shah
2011-11-11 23:18 ` Steve Simon
2011-11-12 4:51 ` Lucio De Re
2011-11-12 5:15 ` Bruce Ellis
2011-11-12 5:36 ` Lucio De Re
2011-11-12 4:49 ` Lucio De Re
2011-11-11 23:38 ` Iruatã Souza
2011-11-12 9:23 ` Bakul Shah
2011-11-13 0:53 ` Bruce Ellis
2011-11-13 4:48 ` Lucio De Re
2011-11-13 5:55 ` Bruce Ellis
2011-11-13 10:08 ` Steve Simon [this message]
2011-11-13 10:30 ` Bruce Ellis
2011-11-13 17:08 ` ron minnich
2011-11-15 21:10 ` Anthony Martin
2011-11-15 21:49 ` David Leimbach
[not found] <CAP6exY+7R9z3uusW683gFCCjvt+t6cZVpq-0TWZL2SiDBbMw3g@mail.gmail.c>
2011-11-11 16:09 ` erik quanstrom
2011-11-11 17:27 ` Lucio De Re
2011-11-11 17:25 ` ron minnich
2011-11-11 18:00 ` Lucio De Re
[not found] <CABT0RTRAXEL454dP+gpC7gYtV9hT7mk+1znEVU0NP4CuKcW=vg@mail.gmail.com>
2011-11-13 22:30 ` Scato Logic
2011-11-13 23:22 ` Bruce Ellis
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bce6ef9f641b86ae4aeb8bccc1daece5@quintile.net \
--to=steve@quintile.net \
/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 NNTP newsgroup(s).