MIME-version: 1.0
Content-type: text/plain; charset=utf-8; format=flowed
Content-transfer-encoding: 7bit
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
            Thunderbird/38.0.1
Message-ID:  <55DBB7F6.1070307@clear.net.nz>
Date:         Mon, 24 Aug 2015 17:33:58 -0700
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: aparsloe <aparsloe@CLEAR.NET.NZ>
Subject: Catcode changes
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
Precedence: list
Envelope-To: <rainer.schoepf@GMX.NET>
Status: R

It has taken me a while to get to grips with \tl_set_rescan:Nnn <tl var> 
{setup} {tokens}, not least the fact that *omission* from the setup 
means "revert to usual catcode". I think this is worth documenting in 
interface3.pdf, since it seems not unreasonable (at least it did to me) 
to suppose that if one has explicitly changed a catcode using 
\tl_set_rescan:Nnn, only a similarly explicit change would revert the 
catcode to its usual value. In particular it would be helpful to 
document the fact that using an empty setup { } reverts everything to 
usual values.

Andrew

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus