Mailing-List: contact dev-help@stdcxx.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@stdcxx.apache.org
Received-SPF: pass (athena.apache.org: domain of msebor@gmail.com designates
 66.249.92.175 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:organization:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding:sender;
        b=WGzrPlusl5mJerNM0XhkmM/LH8fRrly82J+6gYIUS/GQjc8a2zewl0YiveO5/MJ0EZpZU+5mnLgtKhB+K2Z8eCFjU4dzh9ZB0MiYJGFV2Nv/mfStq3ZsVuxquloPnA+QSSqdC917Z0Nvt+vOI9aaPtcVoCb87Pl0J5cpJHQMS9c=
Message-ID: <47BE2E28.3020604@roguewave.com>
Date: Thu, 21 Feb 2008 19:06:32 -0700
From: Martin Sebor <sebor@roguewave.com>
Organization: Rogue Wave Software, Inc.
User-Agent: Thunderbird 2.0.0.9 (X11/20071115)
MIME-Version: 1.0
To: dev@stdcxx.apache.org
Subject: Re: svn commit: r628839 - /stdcxx/trunk/tests/self/0.braceexp.cpp
References: <20080218182449.5B0031A9832@eris.apache.org>
 <15560343.post@talk.nabble.com> <47BB356D.3040708@roguewave.com>
 <2494433f0802211440w7182492co62a7039700aa0609@mail.gmail.com>
 <CFFDD219128FD94FB4F92B99F52D0A499AA7B1@exchmail01.Blue.Roguewave.Com>
In-Reply-To: 
 <CFFDD219128FD94FB4F92B99F52D0A499AA7B1@exchmail01.Blue.Roguewave.Com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: Martin Sebor <msebor@gmail.com>

Travis Vitek wrote:
>  
[...]
> I'm honestly leaning toward implementing the behavior of either csh or
> ksh, and adding support for bash style sequences.

This sounds perfectly reasonable to me. IMO, these are all corner
cases that I suspect we're unlikely to run into in our limited uses
of the function. (As much fun as they are to talk about.)

The one question that we do need to decide is how the function should
deal with whitespace. I.e., whether <pcs-char> in the grammar includes
the set of whitespace characters or whether they are treated as special
delimiters.

Martin