public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Gluszczak, Glenn" <glenn.gluszczak@emc.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Argument parsing with gcc compiled program
Date: Fri, 27 Nov 2015 19:02:00 -0000	[thread overview]
Message-ID: <91DCAC3CB99C724EB365BB64677FBE7B01E08F@MX204CL04.corp.emc.com> (raw)

>* From: Marco Atzeri <marco dot atzeri at gmail dot com>
>* To: cygwin at cygwin dot com
>* Date: Fri, 27 Nov 2015 18:08:44 +0100
>* Subject: Re: Argument parsing with gcc compiled program
>* Authentication-results: sourceware.org; auth=none
>* References: <CAO1jNwu2RXpCn2JuaZEhGaFA4_UTW9dxPxRcoasRuUBwgbRQgA at mail dot gmail dot com> <91DCAC3CB99C724EB365BB64677FBE7B01DFDC >at MX204CL04 dot corp dot emc dot com>
>________________________________________

>On 27/11/2015 17:55, Gluszczak, Glenn wrote:
>On Fri, Nov 27, 2015 at 5:03 PM, Gluszczak, Glenn  wrote:

>Please look at my example again.  The same program compiled with Visual Studio does *not*
>strip out the backslash whether run in cmd.exe or bash.exe.  Other utilities like Perl
>do not strip out the backslash either.  It is only programs I compile with Cygwin gcc that do this.

>So if I compile with MS Visual Studio, binaries do not strip backslashes out of
>arguments whether run in bash or cmd.

>If I compile with Cygwin gcc, backslashes are stripped whether in bash or cmd.

>This looks like a compiler issue to me unless someone knows of an option.

>https://cygwin.com/ml/cygwin/2004-07/msg01036.html


Thanks for the email reference.  Cygwin.dll always strips backslashes so I'm stuck compiling with VS, ok.

--
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

             reply	other threads:[~2015-11-27 17:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-27 19:02 Gluszczak, Glenn [this message]
2015-11-28 10:06 ` Achim Gratz
  -- strict thread matches above, loose matches on Subject: below --
2015-11-26 21:20 Gluszczak, Glenn
2015-11-27 10:10 ` Jan Nijtmans
2015-11-27 16:34   ` Gluszczak, Glenn
2015-11-27 16:55     ` Csaba Raduly
2015-11-27 17:08   ` Gluszczak, Glenn
2015-11-27 17:34     ` Marco Atzeri
2015-11-26 20:15 Gluszczak, Glenn
2015-11-26 20:30 ` Marco Atzeri

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=91DCAC3CB99C724EB365BB64677FBE7B01E08F@MX204CL04.corp.emc.com \
    --to=glenn.gluszczak@emc.com \
    --cc=cygwin@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).