Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Mime-Version: 1.0 (Apple Message framework v928.1)
References: <48C4D4F5.3060503@morningstar2.co.uk>
            <859ec5630809080413t37278f82wb0dfcb4468374183@mail.gmail.com>
            <41780601-0613-4AD5-8D2D-9696EAECD494@gmail.com>
Content-Transfer-Encoding: 8bit
Message-ID:  <314F3461-90F6-4EC0-980A-85319122D382@gmail.com>
Date:         Mon, 8 Sep 2008 21:04:39 +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: \cs:c
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <41780601-0613-4AD5-8D2D-9696EAECD494@gmail.com>
Precedence: list
Status: R

On 08/09/2008, at 8:52 PM, Will Robertson wrote:

> On 08/09/2008, at 8:43 PM, Morten Høgholm wrote:
>
>> There is \cs_use:c (in l3basics I believe).
>
> Ah, this is undocumented.
> I'll add something somewhere.

Looking closer, I see:

\def_new:Npn \use:c #1{\cs:w #1\cs_end:}
\def_new:Npn \cs_use:c #1 { \cs:w#1\cs_end: }

These two functions are used in approximately equal number throughout  
expl3 and the xpackages.

Can I deprecate one of these (i.e., do a search'n'replace across the  
board) to fix this inconsistency? I guess if I had to choose one,  
\cs_use:c would be my pick.

Will