This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Arguments parsing in cygwin executables
- From: Andrey Repin <anrdaemon at yandex dot ru>
- To: Corinna Vinschen <cygwin at cygwin dot com>, cygwin at cygwin dot com
- Date: Fri, 19 Jun 2015 13:33:33 +0300
- Subject: Re: Arguments parsing in cygwin executables
- Authentication-results: sourceware.org; auth=none
- References: <CAMSC8GNk-V8qW3jKLOFayN8HRckOWdpwS26rzG_ofH4O3=s=og at mail dot gmail dot com> <20150619084404 dot GS31537 at calimero dot vinschen dot de> <20150619090148 dot GT31537 at calimero dot vinschen dot de>
- Reply-to: cygwin at cygwin dot com
Greetings, Corinna Vinschen!
>> > BTW, in CYGWIN=glob mode, curly braces are handled wrongly
>> > (c:\cygwin\echo.exe {aa} should return {aa}, not aa; because no , or
>> > .. inside {}).
>>
>> I don't think so. GLOB_BRACE globbing is meant to do brance globbing
>> just as csh does. This doesn't require a comma or anything else within
>> the braces. Try this in tcsh or even bash. The underlying code is
> No, not in bash. I see what you mean. Bash handles that differently
> than [t]csh. However, csh is the obvious role model for this behaviour,
> so if I had to choose who's right and who's wrong, csh (and thus the
> glob original BSD code) is the clear winner.
I would also argue that bash handling is wrong.
But it is historical, and unlikely to change, I guess.
>> (almost) stock FreeBSD code, btw.
--
With best regards,
Andrey Repin
Friday, June 19, 2015 13:32:45
Sorry for my terrible english...
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple