User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2.8)
            Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
References: <4C93A430.1020103@morningstar2.co.uk>           
            <20100917180303.GA7348@oberdiek.my-fqdn.de>           
            <19603.49961.484432.456512@morse.mittelbach-online.de>           
            <4C93DCDA.3010707@morningstar2.co.uk>           
            <19604.28880.24959.737588@morse.mittelbach-online.de>           
            <4C9473D3.1030903@morningstar2.co.uk>
            <19604.32690.377127.814320@morse.mittelbach-online.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID:  <4C948174.7080207@morningstar2.co.uk>
Date:         Sat, 18 Sep 2010 10:08:04 +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: Option parsing bug or 'feature'?
To: LATEX-L@listserv.uni-heidelberg.de
In-Reply-To:  <19604.32690.377127.814320@morse.mittelbach-online.de>
Precedence: list
Status: R

On 18/09/2010 10:00, Frank Mittelbach wrote:
> Option names have no spaces and no braces and so the result of passing such
> stuff is undefined (well not undefined as the behavior is deterministic, but
> there can be "surprising" behaviour for boundary cases). So the result of
> undefined usage doesn't classify as a bug.

Okay, I'll note for future reference that this may or may not work. In 
siunitx v2 I have tried to make all of the options work after load time 
(in \sisetup) partly to avoid the limitations of the optional argument 
to \usepackage.
-- 
Joseph Wright