This is the mail archive of the
mailing list for the Cygwin project.
Re: cygwin programs called from non-cygwin programs mauling \" in args
- From: Yitzchak Scott-Thoennes <sthoenna at efn dot org>
- To: cygwin at cygwin dot com
- Date: Wed, 6 Apr 2005 02:09:03 -0700
- Subject: Re: cygwin programs called from non-cygwin programs mauling \" in args
- Organization: bs"d
- References: <20050113064248.GA2416@efn.org> <20050119233410.GA2888@efn.org> <20050120092613.GB4951@cygbert.vinschen.de>
On Thu, Jan 20, 2005 at 10:26:13AM +0100, Corinna Vinschen wrote:
> 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?
Corinna, have you a chance to think about this? I've come to think that
using the MinGW rules makes most sense.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html