From: Chris Faylor <cgf@cygnus.com>
To: cygwin@sourceware.cygnus.com
Subject: Re: line directives from bison
Date: Mon, 27 Mar 2000 08:56:00 -0000 [thread overview]
Message-ID: <20000327115648.A29423@cygnus.com> (raw)
In-Reply-To: <015701bf980c$bac86cf0$0a32a8c0@rainsound.com>
On Mon, Mar 27, 2000 at 08:51:42AM -0800, Michael O'Brien wrote:
>Hola~
>
>When using bison, the line directives, which are on by default, from the
>command prompt, the resulting file contains:
>
>#line 1 "f:\dir\file"
>
>which is bogus (the \ need to be escaped). So, my options are to either run
>the result through sed replacing '\' with "\\" or not use line directives
>(which make debugging quite a pain)
>
>I'm using the 20.1 version of cygnus. Anyone know if this bug is going to be
>fixed anytime soon?
Don't use backward slashes in your filenames. That should eliminate the
problem.
As far as whether this will be changed anytime soon, the answer is "Not unless
someone submits a patch."
cgf
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
prev parent reply other threads:[~2000-03-27 8:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-27 8:52 Michael O'Brien
2000-03-27 8:56 ` Chris Faylor [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=20000327115648.A29423@cygnus.com \
--to=cgf@cygnus.com \
--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).