Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <199909071904.VAA00530@istrati.zdv.uni-mainz.de>
            <199909101541.QAA22188@mimosa.csv.warwick.ac.uk>
            <199909120954.LAA00439@istrati.zdv.uni-mainz.de>
            <199909122003.UAA09420@rigel.univie.ac.at>
Message-ID:  <14302.23165.67343.509067@n15ux24.nets.de.eds.com>
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@URZ.UNI-HEIDELBERG.DE>
Comments:     Resent-From: Frank Mittelbach <frank.mittelbach@smc.eds.de>
Comments:     Originally-From: Frank Mittelbach <frank.mittelbach@smc.eds.de>
In-Reply-To:  <199909122003.UAA09420@rigel.univie.ac.at>
Date:         Tue, 14 Sep 1999 16:23:57 +0200
From: Frank Mittelbach <frank.mittelbach@SMC.EDS.DE>
Sender: Mailing list for the LaTeX3 project
              <LATEX-L@URZ.UNI-HEIDELBERG.DE>
To: Multiple recipients of list LATEX-L
              <LATEX-L@URZ.UNI-HEIDELBERG.DE>
Subject:      Re: xparse
Status: R

Werner

 >     >   Using characters other than * to indicate variant forms. I can
 >     >   imagine a command with two independent variants, accesed by
 >     >   \foo, \foo*, \foo+, and \foo*+
 >
 >    this could be provided easily enough, eg, S{<symbol-to-scan} and
 >    might indeed be generally useful, any comments?
 >
 > A very nice idea!  I like it.  But the \foo*+ form is too much -- a
 > single character should be sufficient.

you misunderstood, the suggestion was to allow scanning for some
arbitrary symbol (well sort of arbitrary) e.g.

\DeclareDocumentCommand \foo { S{*} S{+} }
   { ... }


the above would  parse

\foo  (returning \BooleanFalse\BooleanFalse)
\foo* (returning \BooleanTrue\BooleanFalse)
\foo+ (returning \BooleanFalse\BooleanTrue)

but of course also

\foo*+ (returning \BooleanTrue\BooleanTrue)


whether this is helpful / sensible to have this extension is another
matter but this would be the functionality

frank