Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
References: <FCD36D2B-F401-4704-9FDD-80204B5FA03D@gmail.com>
            <859ec5630811060730t6d8689t43ec0af09a23b911@mail.gmail.com>
            <887A8F9F-D139-4C9A-B150-759DDB4AB514@gmail.com>
Message-ID:  <F4BE695F-913F-436C-A76B-9E7CB74138FC@gmail.com>
Date:         Sun, 23 Nov 2008 14:34:16 +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: Some implementation details of \let:XX
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <887A8F9F-D139-4C9A-B150-759DDB4AB514@gmail.com>
Precedence: list
Status: R

Hi,

Regardless of my last email, I've now committed a minor change to  
expl3 repository by which all of \let:NN, \glet:NN, \let_new:NN, and  
\glet_new:NN are defined with \def_protected_long_new, and the  
variants are plain old \def_new. (No change, then, to  \let:NN at all.  
Just bringing the others into line.)

The only real change this makes that I'm aware of is that
   \let_new:NN \par \foo
will now complain '\par already defined' rather than 'runaway  
argument'. I think this is sensible since \let:NN itself does allow  
\par.

Let me know if I've missed something :)

Cheers,
Will