User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:6.0.2) Gecko/20110902
            Thunderbird/6.0.2
MIME-Version: 1.0
References: <4E692829.2000003@morningstar2.co.uk>           
            <CAArVCkRdSyDDjKjS=yXrMZ+h+Pr0OQFJ1ZrW-Hdh3j-687QPKw@mail.gmail.com> <4E75B860.40106@morningstar2.co.uk>   
            <CAArVCkSc7cqZ8ZxdSgwpkMD04PdabM3azL=_Kt9n24TPU3XSgQ@mail.gmail.com>           
            <4E75F68E.80004@morningstar2.co.uk>
            <CABk3zN6=oxFObAywYGUWX_JFnFh5fmaK=yo8Lc6oNkXn4VHQjA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-ID:  <4E77332B.1010808@morningstar2.co.uk>
Date:         Mon, 19 Sep 2011 13:18:51 +0100
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: Joseph Wright <joseph.wright@MORNINGSTAR2.CO.UK>
Subject: Re: Removal of previously-notified functions
To: LATEX-L@listserv.uni-heidelberg.de
In-Reply-To:  <CABk3zN6=oxFObAywYGUWX_JFnFh5fmaK=yo8Lc6oNkXn4VHQjA@mail.gmail.com>
Precedence: list
Status: R

On 19/09/2011 08:14, Kevin Godby wrote:
> I'm inclined to agree with Philipp.  Skimming through the existing
> LaTeX 2e packages, it looks like a lot of \newlength lines are
> followed immediately by setting a default value.  In some cases,
> commands are provided to modify the length and in other cases, the
> document author is expected to \setlength them in their preamble.
> Most of the cases that I spot-checked were non-constant values.

As Frank has commented, this is very much how LaTeX2e works but not
necessarily what we'd expect to be dominant for LaTeX3.

> I'm not sure what the LaTeX 3 plans are for the keyval stuff is,
> though.  How would you handle this situation using the LaTeX 3 coding
> style?

For design-level stuff, the template system should be taking a lot of
the work on, while for more flexible stuff there is l3keys. Both are
keyval-based, and separate out 'define' and 'set' stages.

> On the topic of constants:  Aside from the c_ prefix indicating to the
> reader/author that the value is to be constant, is there anything that
> prevents one from changing the value?  How much overhead would it be
> to have the LaTeX 3 macros check for the c_ prefix and throw an error
> if you try to modify the value?

Currently, we don't check this, and the overhead would be I think too
big for production code. I'm hoping we can go down the route of a set of
'debug' DocStrip guards to generate a slow-but-checking version of
LaTeX3 for testing purposes. Something of this idea is seen in the
'check-declarations' option for loading expl3.

> As for the iow_open question, I think that most languages will
> overwrite the existing file by default.  If you want to provide an
> option for appending to the file, I'd create an ioa_open:N macro.

This one seems clear: the arguments for a _new function here are
reasonable. Expect an update to the SVN this week (possibly today,
depends on how busy I am).
-- 
Joseph Wright