On 19 Oct 2007, at 20:12, [EMAIL PROTECTED] wrote:
Unfortunately, for the project I'm working on, I need to build and
use bison 2.1 on Windows (both mks and cygwin), a number of Unix
platforms, and even a mainframe (z/OS). I would like to understand
the bison issue, but " #undef IN" does w
-- Original message --
From: Hans Aberg <[EMAIL PROTECTED]>
> On 19 Oct 2007, at 17:41, [EMAIL PROTECTED] wrote:
>
> >>> I am running into an interesting problem on Windows with Bison
> >>> 2.1. My grammar defines the word IN as a token. When I build on
> >>> Wi
On 19 Oct 2007, at 17:41, [EMAIL PROTECTED] wrote:
I am running into an interesting problem on Windows with Bison
2.1. My grammar defines the word IN as a token. When I build on
Windows, there is a file which includes the generated gram.h after
including Microsoft's header WinDef.h. I'm using
On Fri, 19 Oct 2007, [EMAIL PROTECTED] wrote:
> Yes, using "#undef IN" after the inclusion of WinDef.h works, but it
> seems like a bit of a hack. By getting "those who wrote it to fix
> it", if you mean WinDef.h, it's a header from Visual Studio.
> Somehow, I doubt that I could get Microsoft to
-- Original message --
From: Hans Aberg <[EMAIL PROTECTED]>
>
> On 19 Oct 2007, at 00:42, [EMAIL PROTECTED] wrote:
>
> > I am running into an interesting problem on Windows with Bison
> > 2.1. My grammar defines the word IN as a token. When I build on
> > W
On 19 Oct 2007, at 00:42, [EMAIL PROTECTED] wrote:
I am running into an interesting problem on Windows with Bison
2.1. My grammar defines the word IN as a token. When I build on
Windows, there is a file which includes the generated gram.h after
including Microsoft's header WinDef.h. I'm
I am running into an interesting problem on Windows with Bison 2.1. My grammar
defines the word IN as a token. When I build on Windows, there is a file which
includes the generated gram.h after including Microsoft's header WinDef.h. I'm
using Visual Studio .NET 2003. Unfortunately, that head
