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
Sender: Mailing list for the LaTeX3 project <[log in to unmask]>
Date: Fri, 23 Oct 2009 14:23:47 +0100
Reply-To: Mailing list for the LaTeX3 project <[log in to unmask]>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
In-Reply-To: <[log in to unmask]>
Content-Type: text/plain; charset=ISO-8859-1
From: Joseph Wright <[log in to unmask]>
Parts/Attachments: text/plain (48 lines)
Lars Hellström wrote:
> From my point of view, there were two issues.
> The first issue is that the given "return value register"
> \l_xparse_arg_toks is a toks when (in my experience) values (at least
> non-numeric values) are more commonly returned by defining a macro. This
> thus has to do with the ability to reuse existing code (in packages and
> such).

Yes, I can certainly see that point.

> The second issue is that the name \l_xparse_arg_toks would not fit in at
> all if using \DeclareDocumentCommand in e.g. the preamble of a document;
> one would have to fiddle around with the catcodes just to be able to
> type it, and the name is unintuitive.

I'd tend to regard processing an argument as something that is going to
show up mainly in blocks of code, not ad hoc definitions for functions
in a document. However, we loose nothing by allowing some flexibility.

> I suppose a compromise could be to use a fixed command name in the same
> class as \DeclareDocumentCommand -- e.g. \XparseResult or
> \XparseProcessorResult -- and do
>   \let\XparseResult=\l_xparse_arg_toks
> just before each processor; then the user can use this high-level name
> and not have to worry about the low-level LaTeX3 name. Furthermore this
> provides support for mixing macro- and toks-setting processors, as code
> that ends up doing \XparseResult={...} will access the toks register,
> whereas code that ends up doing \def\XparseResult{...} just breaks the
> association of \XparseResult to \l_xparse_arg_toks (as opposed to
> breaking xparse as a whole). Either way, V-expanding \XparseResult will
> recover what had been stored.

Taking this idea, I'd probably favour something that doesn't include
"xparse" as a document-level function: perhaps \ProcessedArgument or
\ProcessingResult? If I say that it will initially be a toks (for each
parsing run), then you can do


etc. Would that work?
Joseph Wright