Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Mon, 27 Mar 2000 11:56:48 -0500 To: cygwin AT sourceware DOT cygnus DOT com Subject: Re: line directives from bison Message-ID: <20000327115648.A29423@cygnus.com> Reply-To: cygwin AT sourceware DOT cygnus DOT com Mail-Followup-To: cgf AT cygnus DOT com, cygwin AT sourceware DOT cygnus DOT com References: <015701bf980c$bac86cf0$0a32a8c0 AT rainsound DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.8i In-Reply-To: <015701bf980c$bac86cf0$0a32a8c0@rainsound.com>; from mobrien@pixar.com on Mon, Mar 27, 2000 at 08:51:42AM -0800 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 AT sourceware DOT cygnus DOT com