MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <87wsv6odr8.fsf@buckbeak.hogwarts>
            <18141.38684.704361.46277@morse.mittelbach-online.de>
            <op.tx4553qyjli536@newhost71-038.imm.dtu.dk>
            <87sl5uno7u.fsf@buckbeak.hogwarts>
            <18141.51596.255158.574401@morse.mittelbach-online.de>
            <87ir6qng8e.fsf@buckbeak.hogwarts>
            <18142.20142.549886.908550@morse.mittelbach-online.de>
            <op.tx6qpyb7jli536@wnn24194.wireless.dtu.dk>
            <18148.25382.129327.738753@morse.mittelbach-online.de>
            <878x7douyv.fsf@buckbeak.hogwarts>
Message-ID:  <18151.2368.779712.110953@morse.mittelbach-online.de>
Date:         Tue, 11 Sep 2007 23:31:44 +0200
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: Frank Mittelbach <frank.mittelbach@LATEX-PROJECT.ORG>
Subject: Re: l3prop -- syntax and functionality change
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <878x7douyv.fsf@buckbeak.hogwarts>
Precedence: list
Status: R

Andreas,

thanks

 > So far I have noticed the following.
 > 
 > * In l3expan the following definitions are missing
 > 
 >    \def_new:Npn \exp_args:NNnx {\::N\::n\::x\:::}
 >    \def_new:Npn \exp_args:NNox {\::N\::o\::x\:::}
 >    \def_new:Npn \exp_args:NNoo {\::N\::o\::o\:::}

good point. that module needs a bit mor standardization anyway to have all
typical 1-5 arg expansions predefined

 > * The docu of l3prop says that \prop_map_inline refers to the
 >   arguments via ##1 and ##2. But it should be #1 and #2.

fixed

 > * What is \prop_gput:Ooo for? Hasn't got \prop_gput:Noo the
 >   same functionality? (Let alone that \prop_gput:Ooo doesn't
 >   work, yet.)

O in contrast to o means single expanion on an input which is a single token
ie no braces around it.

\tlp_new:N \l_tmp_tlp
\prop_new:N \g_foo_prop

\tlp_set:Nn \l_tmp_tlp {\g_foo_prop}

\prop_gput:Ooo \l_tmp_tlp ...

don't ask me why that is predefined. perhaps i needed it for the xor module at
one stage ... it is pretty weird and i don't think there is much use in
setting it up unless there is actually a use for it.

and then there is the question that you say it doesn't work ... perhaps i
better look at that one.

frank