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 lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <16431767.post@talk.nabble.com>
Date: Tue, 1 Apr 2008 16:54:31 -0700 (PDT)
From: Martin Sebor <sebor@roguewave.com>
To: dev@stdcxx.apache.org
Subject: Re: spaces in rw_xxx_expand()
In-Reply-To: <47EFD7E2.8000402@roguewave.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <47EFD7E2.8000402@roguewave.com>


PING? Should I open an issue for this or is it something you're
already working on or planning to?


Martin Sebor wrote:
> 
> In the shell, spaces that are otherwise treated as separators can
> be either escaped or quoted to have them interpreted as ordinary
> characters. The rw_xxx_expand() functions let me escape spaces but
> they don't seem to like quoting. For example, the shell expands
> the following three strings to the same result:
> 
>      "a{b\ c,d}"    ==> "ab c ad"
>      "a{b' 'c,d}"
>      "a{b" "c,d}"
> 
> but rw_brace_expand() fails on the last two. It should work the
> same as the shell.
> 
> In the change below I've enhanced the 0.braceexpand.cpp test to
> exercise a number of (passing) test cases including plan as well
> as escaped whitespace:
> 
> http://svn.apache.org/viewvc?rev=642790&view=rev
> 
> I think the same test cases should be added for quoted whitespace.
> 
> Martin
> 
> 

-- 
View this message in context: http://www.nabble.com/spaces-in-rw_xxx_expand%28%29-tp16385194p16431767.html
Sent from the stdcxx-dev mailing list archive at Nabble.com.