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, 24 Oct 2008 10:43:05 +0200
Content-Disposition: inline
Reply-To: Mailing list for the LaTeX3 project <[log in to unmask]>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
In-Reply-To: <[log in to unmask]>
Content-Type: text/plain; charset=ISO-8859-1
From: Morten Høgholm <[log in to unmask]>
Parts/Attachments: text/plain (32 lines)
On Mon, Oct 20, 2008 at 6:16 PM, Frank Mittelbach
<[log in to unmask]> wrote:
> Joseph Wright writes:
>  > Will Robertson wrote:
>  > > I noticed that recently too. I think it would be better to remove that
>  > > variant in the expl3 syntax, since it doesn't seem like it adds much of
>  > > importance but it adds a bit of obfuscation.
>  >
>  > As you probably guessed from the question, that would be my preferred
>  > solution too.
> I agree with both of you.let's mark it as obsolete for now and wait for Morten
> to speak up who introduced it (I guess)

It is used in a few cases such as

\def_long:Npn \tlp_if_in:NnTF #1#2{
  \def_long:Npn\tmp:w ##1 #2 ##2\q_stop{
  \exp_after:NN \tmp:w #1 #2 \q_no_value \q_stop

If there was no FT variant, this function would either have to read
the TF arguments twice or the quark test would have to be done

The FT variant was never meant to be heavily used - just a shuffle
variant so to speak.