LATEX-L Archives

Mailing list for the LaTeX3 project


Options: Use Classic View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Content-Transfer-Encoding: 7bit
Sender: Mailing list for the LaTeX3 project <[log in to unmask]>
From: Joseph Wright <[log in to unmask]>
Date: Wed, 2 Sep 2009 20:26:37 +0100
Content-Type: text/plain; charset=ISO-8859-1
MIME-Version: 1.0
Reply-To: Mailing list for the LaTeX3 project <[log in to unmask]>
Parts/Attachments: text/plain (20 lines)
Hello all,

One question occurs to me about xparse "processors". I've provided one
that splits on a comma, \xparse_process_comma_split:n. I wonder what the
behaviour of this type of function should be if the input is not of the
correct form. At the moment, if you apply a processor to an optional
argument and no value is given, the special \NoValue token is left
alone.  The normal behaviour for this function is:

\xparse_process_comma_split:n { 1,2 } => {1} {2}

but what should happen with

\xparse_process_comma_split:n { 12 }

A the moment you get "{12} \NoValue" so that exactly two results are
returned. Should you get perhaps just \NoValue, or something else?
Joseph Wright