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>
            <18151.2368.779712.110953@morse.mittelbach-online.de>
            <87642gamew.fsf@buckbeak.hogwarts>
Message-ID:  <18152.18272.17469.802061@morse.mittelbach-online.de>
Date:         Wed, 12 Sep 2007 22:09:04 +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:  <87642gamew.fsf@buckbeak.hogwarts>
Precedence: list
Status: R

Andreas,
 
> > 
 > > \tlp_new:N \l_tmp_tlp
 >   ^^^^^^^^^^
 > ;-)
 > I am doing this mistake frequently. But there is only a
 > \tlp_clear_new:N. Maybe there really should exist a \tlp_new:N.

hm yes, it is somewhat inconsistent to have the tlp initialisation to take a
default value while normally that isn't the case.

have added \tlp_new:N  (which is equiv to \tlp_new:Nn #1 {} )

 > > \prop_new:N \g_foo_prop
 > > 
 > > \tlp_set:Nn \l_tmp_tlp {\g_foo_prop}
 > > 
 > > \prop_gput:Ooo \l_tmp_tlp ...
 > 
 > 
 > Hmm... But this could be done with \prop_gput:Noo as well.

that could only be done if you know that \prop_gput:Noo expand its argument
internally due to its implementation and you use this fact. so you use a
feature of the implementation which may not be there tomorrow

just assume for a moment we would built in checks for variables to be checked
for type or local global state then passing "\l_tmp_tlp" would fail on both
accounts (not that i propose that)

cheers
frank