From: Chris Faylor <cgf@cygnus.com>
To: John R Hanson <JRSON@NetZero.Net>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: cygwin->msvcrt argv expansion algorithems
Date: Sun, 12 Dec 1999 13:38:00 -0000 [thread overview]
Message-ID: <19991212163831.B826@cygnus.com> (raw)
In-Reply-To: <3853f8e4.51785625@smtp.netzero.net>
On Sun, Dec 12, 1999 at 07:43:34PM +0000, John R Hanson wrote:
>You would know better than I where these need to be slotted
>into the cygwin .dll.
I guess if I took some time, I could probably figure out what "these"
are. This seems to have something to do with command line quoting,
obviously. And, you want to plug it into cygwin somewhere.
But I'm sorry to say that I'm not going to take time to investigate
hundred of lines of code, especially when I have no clear idea what
it's for.
If this is intended to replace one of cygwin's quoting methods, it's
unlikely that I'd consider doing that without an extremely compelling
rationale for doing so. "It doesn't handle all of the cases that MSVC
does" is *not* a reason for throwing everything away, btw.
Sorry,
Chris
>--- Cut Here ----------------------------------------------------------
> /* this is an example program for encoding and decoding
> command lines to be used when starting a subprocess
> via CreateProcess
> compile with
> gcc -oCreateP CreateP.c
> */
>[snip]
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
WARNING: multiple messages have this Message-ID
From: Chris Faylor <cgf@cygnus.com>
To: John R Hanson <JRSON@NetZero.Net>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: cygwin->msvcrt argv expansion algorithems
Date: Fri, 31 Dec 1999 13:28:00 -0000 [thread overview]
Message-ID: <19991212163831.B826@cygnus.com> (raw)
Message-ID: <19991231132800.iOo6cWbPTNsR_2aCb5B2njGFDdWyb38eyVqGAlBawqw@z> (raw)
In-Reply-To: <3853f8e4.51785625@smtp.netzero.net>
On Sun, Dec 12, 1999 at 07:43:34PM +0000, John R Hanson wrote:
>You would know better than I where these need to be slotted
>into the cygwin .dll.
I guess if I took some time, I could probably figure out what "these"
are. This seems to have something to do with command line quoting,
obviously. And, you want to plug it into cygwin somewhere.
But I'm sorry to say that I'm not going to take time to investigate
hundred of lines of code, especially when I have no clear idea what
it's for.
If this is intended to replace one of cygwin's quoting methods, it's
unlikely that I'd consider doing that without an extremely compelling
rationale for doing so. "It doesn't handle all of the cases that MSVC
does" is *not* a reason for throwing everything away, btw.
Sorry,
Chris
>--- Cut Here ----------------------------------------------------------
> /* this is an example program for encoding and decoding
> command lines to be used when starting a subprocess
> via CreateProcess
> compile with
> gcc -oCreateP CreateP.c
> */
>[snip]
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~1999-12-12 13:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-12 12:33 John R Hanson
1999-12-12 13:38 ` Chris Faylor [this message]
1999-12-12 14:04 ` John R Hanson
1999-12-12 17:06 ` Chris Faylor
1999-12-31 13:28 ` Chris Faylor
1999-12-31 13:28 ` John R Hanson
1999-12-31 13:28 ` Chris Faylor
1999-12-31 13:28 ` John R Hanson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19991212163831.B826@cygnus.com \
--to=cgf@cygnus.com \
--cc=JRSON@NetZero.Net \
--cc=cygwin@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).