From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mimir.eigenstate.org ([206.124.132.107]) by ewsd; Wed Oct  7 00:46:12 -0400 2020
Received: from abbatoir.fios-router.home (pool-74-101-2-6.nycmny.fios.verizon.net [74.101.2.6])
	by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id 9a6514c0 (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO);
	Tue, 6 Oct 2020 21:46:02 -0700 (PDT)
Message-ID: <73478730890303D4AEBA1B06EC1795B9@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
From: ori@eigenstate.org
In-Reply-To: <01DB736907F1AF8292BF2D9C25564677@ewsd.inri.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: responsive cloud descriptor 

>> 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.