From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-patches@cygwin.com
Subject: Re: Re: [PATCH v4 1/3] Cygwin: rewrite and make public cmdline parser
Date: Tue, 13 Oct 2020 14:14:41 +0200 [thread overview]
Message-ID: <20201013121441.GN26704@calimero.vinschen.de> (raw)
In-Reply-To: <33c7b23a-5f59-bcaa-3b0a-6e6d4bc4f30b@aosc.io>
On Sep 24 16:39, Mingye Wang (Artoria2e5) wrote:
> On 2020/9/7 17:39, Corinna Vinschen wrote:
> >
> > Nope, we won't do that. The command line parsing is an internal
> > thing, and we won't export arbitrary internal functions using
> > their own symbol. *If* we should export this stuff at all, which
> > I highly doubt as necessary, it should use the cygwin_internal API.
>
> The idea is that the sort of thing get reimplemented incorrectly a lot, and
> since we have the extra @file feature and the Unix glob it would be nice to
> allow other people to use it. Win32 has CommandLineToArgvW, so I figured it
> wouldn't be too strange to have.
In contrast to stock Windows executables we already have a valid argv.
Corinna
prev parent reply other threads:[~2020-10-13 12:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-05 5:27 Mingye Wang
2020-09-05 5:27 ` [PATCH v4 2/3] regparm: make code highlight happy Mingye Wang
2020-09-07 9:11 ` Corinna Vinschen
2020-09-05 5:27 ` [PATCH v4 3/3] testsuite: don't strip dir from obj files Mingye Wang
2020-09-07 9:14 ` Corinna Vinschen
2020-11-07 12:12 ` [PATCH v5] Cygwin: rewrite cmdline parser Mingye Wang
2020-11-07 12:12 ` [PATCH] " Mingye Wang
2020-11-09 10:04 ` Corinna Vinschen
2021-05-13 13:15 ` [PATCH v6] " Mingye Wang
2021-05-13 13:28 ` Mingye Wang
2021-05-14 19:38 ` Johannes Schindelin
2021-05-17 11:03 ` Corinna Vinschen
2020-09-07 9:39 ` [PATCH v4 1/3] Cygwin: rewrite and make public " Corinna Vinschen
2020-09-24 8:39 ` Mingye Wang (Artoria2e5)
2020-10-13 12:14 ` Corinna Vinschen [this message]
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=20201013121441.GN26704@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-patches@cygwin.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).