Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1081)
References: <7255173980814043.WA.blflatexgmail.com@listserv.uni-heidelberg.de>
            <D7936EC9-DDF7-4BB4-B3BF-E3FDE88A8499@gmail.com>
            <AANLkTi=oyFd9wq289rwdgktb93saymtHCoCM0jSQ=Zyb@mail.gmail.com>
Content-Transfer-Encoding: 8bit
Message-ID:  <E131E382-E245-4A9D-919F-9EF63ED70B17@gmail.com>
Date:         Mon, 10 Jan 2011 12:08:31 +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: Verbatim and xparse (yet again :)
To: LATEX-L@listserv.uni-heidelberg.de
In-Reply-To:  <AANLkTi=oyFd9wq289rwdgktb93saymtHCoCM0jSQ=Zyb@mail.gmail.com>
Precedence: list
Status: R

Hi Bruno,

Just a quick reply, sorry.

On 09/01/2011, at 8:53 AM, Bruno Le Floch wrote:

>   \cprotect\section[...\verb|#&!|...]{...\verb|#&!|...}  How does
>> \cprotect know what to read in?
> 
> I propose the following: \cprotect[argument specification], where the
> argument specification is like in xparse. Your example would become
> 
>   \cprotect[om]\section[...\verb|#&!|...]{...\verb|#&!|...}
> 
> If the optional argument is missing, \cprotect\foo could proceed like
> this: [snip]

This seems like a sensible approach.
You could also scan ahead for opening braces and assume if they exist they're an argument for the macro. (Not sure if this would be more or less reliable than the other tests you proposed, though.)


> - Maybe also add the case of internal commands (\foo:Nn, or whatever),
>  where the argument specification would be read from the name? Although
>  I don't expect any use for that: internals should not need
>  \cprotect. Should they?

I doubt it. FWIW, for expl3 functions you can use \cs_get_arg_count_from_signature:N to find out how many arguments they take. (This is used internally for commands like \cs_new:Nn)

-- Will