User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101
            Thunderbird/24.5.0
MIME-Version: 1.0
References: <538C959C.3060904@morningstar2.co.uk>                      
            <538CA727.1000203@morningstar2.co.uk> <538D0DD2.2090106@nag.co.uk>
            <538D8F99.3010400@morningstar2.co.uk>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: None (: nag.co.uk does not designate permitted sender hosts)
Message-ID:  <538DBBC9.9010905@nag.co.uk>
Date:         Tue, 3 Jun 2014 13:12:57 +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: David Carlisle <davidc@NAG.CO.UK>
Subject: Re: 'Preseting' keys
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <538D8F99.3010400@morningstar2.co.uk>
Precedence: list
Envelope-To: <rainer.schoepf@GMX.NET>
Status: R

On 03/06/2014 10:04, Joseph Wright wrote:
> I can see how one might set up a 'preset if not already set' approach,
> but I'm not sure how it's different from simply starting off with a
> default.


yes true but probably in the usual case where each key setting happens
in a local group, and only happens once in that group then any kind of 
presetting
is probably equivalent to just setting the defaults initially at the 
outer level.
(Apart from side effects like writing to log, or global increments that 
expose
the order or number of times, the key has been set)

David