Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1081)
References: <4C967C9B.5010706@gmx.de>           
            <71ED7A5B-DE11-45D9-9785-95A1DC795080@gmail.com>
            <19607.3907.558898.274512@morse.mittelbach-online.de>
            <4C9711F9.8070804@morningstar2.co.uk>
Content-Transfer-Encoding: 8bit
Message-ID:  <488E7AB8-0048-47BC-9D5F-8DD907536420@gmail.com>
Date:         Mon, 20 Sep 2010 18:00:31 +0930
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@listserv.uni-heidelberg.de>
Sender: Mailing list for the LaTeX3 project <LATEX-L@listserv.uni-heidelberg.de>
From: Will Robertson <wspr81@GMAIL.COM>
Subject: Re: boolean expressions in ExplSyntaxNames
To: LATEX-L@listserv.uni-heidelberg.de
In-Reply-To:  <4C9711F9.8070804@morningstar2.co.uk>
Precedence: list
Status: R

On 20/09/2010, at 5:19 PM, Joseph Wright wrote:

> On 20/09/2010 08:37, Frank Mittelbach wrote:
>> Personally, I would think that it isn't needed at all. Instead I would suggest
>> to either drop it totally so that with expl code ~ always needs to be used for
>> entering spaces or provide
> 
> I'm with Frank on this. One clear set of switches (\ExplSyntaxOn/Off) is enough for me, and we avoid the possibility of more things 'falling through the gap'.

I'm not against dropping \ExplSyntaxNames(On/Off). My only perceived benefit for them is that package authors can use them inside their own packages without having to deal with any spaces->ignored issue. But something like \ExplObeySpaces(On/Off) deals with this nicely.

What happens if \ExplObeySpaces(On/Off) occurs outside of a \ExplSyntax(On/Off) pair? (I guess it'd be a no-op, but just covering bases.)

-- Will