From: ori@eigenstate.org
To: sl@stanleylieber.com, 9front@9front.org
Subject: Re: [9front] new rc parser: do we want it?
Date: Tue, 06 Oct 2020 21:46:01 -0700 [thread overview]
Message-ID: <73478730890303D4AEBA1B06EC1795B9@eigenstate.org> (raw)
In-Reply-To: <01DB736907F1AF8292BF2D9C25564677@ewsd.inri.net>
>> and unquoted '=' is allowed after the
>> first word:
>>
>> echo a=b
>
> fwiw, when aiju suggested this a couple years ago i made a
> big stink about how this breaks the predictable quoting
> rules, but if rsc is dispensing with regularity, i don't
> know what to say anymore. i suppose it's just one more thing to
> remember.
>
> sl
I agree. I'm not sure how I feel about making '=' parsing
stateful. It matters more in plan9port, where a lot of
tools these days expect:
--long-fucking-arg-name=thing
The free caret handling is slighty more interesting to me,
I've been tripped up by x`{y} getting a caret, but `{y}x
not getting one -- and it feels messy.
I also find the yacc grammar more readable than the C
rewrite.
next parent reply other threads:[~2020-10-07 4:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <01DB736907F1AF8292BF2D9C25564677@ewsd.inri.net>
2020-10-07 4:46 ` ori [this message]
2020-10-07 13:06 ` kvik
[not found] <5EF01FE4B564E504DD635D7E391EE0C8@ewsd.inri.net>
2020-10-12 20:44 ` Romano
2020-10-15 10:11 ` Ethan Gardener
2020-10-15 12:11 ` Stanley Lieber
2020-10-15 16:41 ` Romano
2020-10-15 17:22 ` Anthony Martin
2020-10-15 23:14 ` Roman Shaposhnik
2020-10-15 23:32 ` Stanley Lieber
[not found] <1975289B8C108B2FCF360524D16AA25B@ewsd.inri.net>
2020-10-07 10:00 ` Ethan Gardener
2020-10-07 3:15 ori
2020-10-07 3:54 ` [9front] " sl
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=73478730890303D4AEBA1B06EC1795B9@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
--cc=sl@stanleylieber.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 NNTP newsgroup(s).