This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: cygwin programs called from non-cygwin programs mauling \" in args
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 20 Jan 2005 10:26:13 +0100
- Subject: Re: cygwin programs called from non-cygwin programs mauling \" in args
- References: <20050113064248.GA2416@efn.org> <20050119233410.GA2888@efn.org>
- Reply-to: cygwin at cygwin dot com
Yitzchak,
On Jan 19 15:34, Yitzchak Scott-Thoennes wrote:
> > $ ./nocygparent cygchild
> > [a\b"c]
>
> Can anybody else confirm this?
I can. I already had a look into this. The command line handling in
Cygwin is different from the command line handling in MingW or, FWIW,
VC++ CLI applications.
The question is if we really should align the rules how a native
command line is evaluated by a Cygwin process should be aligned
to Windows rules or not.
There are three arguments to consider:
- Using Windows/MingW rules lowers the surprise.
- Changing the rules at all breaks backward compatibility.
- Why shouldn't Cygwin applications use their own rules which seem
more appropriate for a POSIX application?
Btw., if you want the same result as for the noncygchild, just quote:
$ cygchild "a\"b\"c"
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader mailto:cygwin@cygwin.com
Red Hat, Inc.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/