Re: [Mingw-users] Problem with gcc

[<dan...@ya...>]

 --- Wu Yongwei <ad...@ne...> wrote: > I believe it is a bug. Adding "else"
to the last line of open_file will work
> in GCC 2.95.3, too:
> 
> void open_file (ofstream& out, const char *fname)
> {
>     string name = fname;
>     out.open(name.c_str());  // Try to open
>     if (out.good()) return;  // found it!
>     else throw exception();
> }
> 
That's an old C++ lexer bug that used to surface every now and again.  IIRC, it
was die to preprocessor adding __FILE__ information and that getting mixed up
with comments and with attempts to forgive windows for its backslashes in
filenames.  

Danny

> I am completely puzzled how it happened. Maybe you should consider GCC 3.
> 
> Best regards,
> 
> Wu Yongwei
> 
> Ryan Nunn <tri...@me...> writes:
> 
> > I'm one of the programmers on Exult (http://exult.sf.net) and we've
> > been tracking a problems with long filenames in windows for quite a
> > long time. I've managed to sort of work out what is causing the
> > problem and it appears that it might be a compiler bug. I'm currently
> > using MinGW 1.1 that is dated 2001-09-20. I've also tried with
> > gcc-2.95.3-20011106-beta and it produces the same behaviour.
> 
> ...
> 
> 
> _______________________________________________________________
> 
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
> 
> _______________________________________________
> MinGW-users mailing list
> Min...@li...
> 
> You may change your MinGW Account Options or unsubscribe at:
> https://lists.sourceforge.net/lists/listinfo/mingw-users 

http://www.sold.com.au - The Sold.com.au Big Brand Sale
- New PCs, notebooks, digital cameras, phones and more ... Sale ends June 12