Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes
Mime-Version: 1.0 (Apple Message framework v929.2)
References: <495160FA.8000004@morningstar2.co.uk>                      
            <9EECA5EE-12A7-4C01-8311-7658BD3E8E04@gmail.com>                   
            <op.umx28toejli536@macintosh.local>                      
            <21363E65-E3FB-4495-A94E-6789AC0619A0@gmail.com>                   
            <18778.35736.43421.950797@morse.mittelbach-online.de>           
            <8A5C4EC7-9242-4A0E-9644-7BCE1BA029CC@gmail.com>
            <495CB38E.4060400@morningstar2.co.uk> <495CBF58.4090208@gmx.de>
Content-Transfer-Encoding: 8bit
Message-ID:  <7E1CEE5E-2BF3-44AB-905D-6C3260D04765@gmail.com>
Date:         Fri, 2 Jan 2009 00:17:12 +1030
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: Back to "token list" nomenclature; was Re: \tlist_if_eq:nn
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <495CBF58.4090208@gmx.de>
Precedence: list
Status: R

On 01/01/2009, at 11:34 PM, Arno Trautmann wrote:

> But then I would say \catcode =12 to everything else, excluding only \
> and maybe {} for grouping. Maybe even the meaning of % and \% could be
> interchanged: % in normal Text and \% as comment?
> Or is that too much changed?…

I'd definitely like to explore ideas like this.
I've vaguely thought in the past what it would take to get {} braces  
as having  catcode other. I'm not sure it's feasible but I think it  
would sure be nice :)

At this stage, however, we can just leave it as vague plans...

Will