[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Tinycc-devel] Parsing bug
From: |
Rob Landley |
Subject: |
Re: [Tinycc-devel] Parsing bug |
Date: |
Mon, 14 May 2007 01:48:58 -0400 |
User-agent: |
KMail/1.9.1 |
On Sunday 13 May 2007 4:37 am, Philippe Ribet wrote:
> >>tcc failed to parse such code because of the "\" character.
> >>
> >>#ifdef WIN32
> >># include <windows.h>
> >># include <gl\glaux.h>
> >>#else
> >># include <X11/Xlib.h>
> >># include <GL/glx.h>
> >>#endif
> >>
> >This was another one of the grischka fixes, but I haven't been tracking
> >Windows stuff because I have neither a windows machine, nor much interest
in
> >the platform.
> >
> My point was to compile on Linux systems code written for portability.
1) The #include <gl\glaux.h> doesn't get parsed on Linux systems because the
#ifdef prevents everything until the #else from being looked at. So if your
concern is "to compile on Linux systems", then the answer is "it does".
2) I just tried it and it complained about putting a space between the # and
the include, which I agree is a stupid thing to do but which C apparently
allows.
But that's a different bug.
Rob