From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] email header screwup (and fix)
Date: Mon, 13 Sep 2010 13:37:00 -0400 [thread overview]
Message-ID: <e07f72ef033647d79ab8837a7684b3f6@ladd.quanstro.net> (raw)
In-Reply-To: <AANLkTikE2SkyyHYPepQGaRRUv8ymP6F5RSx3SXVcZXXH@mail.gmail.com>
> or change the grammar not to need unlimited stack space.
> it says
yes. you're right. i should have fixed this properly
before posting.
> fields : '\n'
> { yydone = 1; }
> | field '\n'
> | field '\n' fields
> ;
>
> but i think you can change it to
>
> fields : fieldlist '\n'
> { yydone = 1; }
> ;
>
> fieldlist :
> | fieldlist field '\n'
> ;
i actually used this to avoid shift/reduce conflict
warnings
msg : fields
| unixfrom '\n' fields
;
fields : fieldlist '\n'
{ yydone = 1; }
;
fieldlist : field '\n'
| fieldlist field '\n'
;
- erik
prev parent reply other threads:[~2010-09-13 17:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-09 20:13 erik quanstrom
2010-09-11 22:15 ` Russ Cox
2010-09-13 17:37 ` erik quanstrom [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e07f72ef033647d79ab8837a7684b3f6@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.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).