Re: malloc: bison-2.1+, prototype mismatch vs. stdlib.h (C++ mode)

I've just encountered a problem where the compiler rejects bison's prototype for "void* malloc(YYSIZE_T);" because it doesn't match with , which looks like "void* malloc(size_t) __THROW ... ;" (ubuntu7). The problem only manifests when compiling the resulting source file as in C++ (otherwise,

Re: malloc: bison-2.1+, prototype mismatch vs. stdlib.h (C++ mode)

On 19 Oct 2007, at 21:54, David Fang wrote: I've just encountered a problem where the compiler rejects bison's prototype for "void* malloc(YYSIZE_T);" because it doesn't match with , which looks like "void* malloc(size_t) __THROW ... ;" (ubuntu7). The problem only manifests when compili

malloc: bison-2.1+, prototype mismatch vs. stdlib.h (C++ mode)

Hi, I've just encountered a problem where the compiler rejects bison's prototype for "void* malloc(YYSIZE_T);" because it doesn't match with , which looks like "void* malloc(size_t) __THROW ... ;" (ubuntu7). The problem only manifests when compiling the resulting source file as in C++ (other

Re: Interesting problem with bison on Windows

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

Re: Interesting problem with bison on Windows

-- 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

Re: Interesting problem with bison on Windows

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

Re: Interesting problem with bison on Windows

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

Re: Interesting problem with bison on Windows

-- 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

Re: Interesting problem with bison on Windows

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

Re: bison 1.875c is incompatible to 1.35

Fix the code of your program. Since you do not give any clues of what the problem is, nobody can help. Hans Aberg On 16 Oct 2007, at 18:11, Baruch Gudesblat wrote: Hello, all. I have some version incompatible problem with bison application. Help, please. Details: My application (Verilog