Re: Bison COPYING confusion

2005-06-07 Thread Aaron Jackson
On Jun 7, 2005, at 11:12 PM, Talin wrote: Unfortunately, having the licensing terms appear only in the program output places a signficant barrier to a legal analysis of the licensing terms. The way my company's evaluation process works is that I can't simply compile bison myself, generate th

Re: Bison COPYING confusion

2005-06-07 Thread Talin
Unfortunately, having the licensing terms appear only in the program output places a signficant barrier to a legal analysis of the licensing terms. The way my company's evaluation process works is that I can't simply compile bison myself, generate the output file, and email a copy of it to ou

bison 2.0 for windows

2005-06-07 Thread hz kto
I wanted to get bison 2.0 to make use of %destructor ferature, but there doesn't seem to be support for windows compilation from the looks of the scripts and readme files. Or am I missing something? In readme it says that DOS buils is probably broken right now. Is anybody compiling for windows?

bison 2.0 for windows

2005-06-07 Thread hz kto
I wanted to get bison 2.0 to make use of %destructor ferature, but there doesn't seem to be support for windows compilation from the looks of the scripts and readme files. Or am I missing something? In readme it says that DOS buils is probably broken right now. Is anybody compiling for windows?

Re[2]: memory leaks

2005-06-07 Thread hz kto
If I have a list like this wouldn't I run into the problem when, a parent node deletes some child nodes, then when I come across this child in the list, I will crash since it has been deleted already? Ugrading to 2.0 is not easy, since different parts of software are using Bison, which is slight

Re: Additional Parameter to %merge function in glr-parsers

2005-06-07 Thread Laurence Finston
On Tue, 7 Jun 2005, Michel Rosien wrote: > Thanks for the reply You're welcome. > > > If it's not possible, and you only call 'yyparse()' once, > > then I think you might as well use a globally or statically declared > > pointer to point to the object referenced by your parameter. > > This is wh

Re: Additional Parameter to %merge function in glr-parsers

2005-06-07 Thread Michel Rosien
Thanks for the reply If it's not possible, and you only call 'yyparse()' once, then I think you might as well use a globally or statically declared pointer to point to the object referenced by your parameter. This is what I do as a 'quick hack' now but doesn't it kind of defeat the purpose of

Re: memory leaks

2005-06-07 Thread Laurence Finston
On Tue, 7 Jun 2005, hz kto wrote: > > I am using C++ with bison 1.25, so it does not have %destructor. I cannot > rely on > garbage collecting, so I have to free everything myself. > Also I do not have common base class for all parse tree nodes (so I can't have > a storage for all parse tree node

Re: Additional Parameter to %merge function in glr-parsers

2005-06-07 Thread Laurence Finston
On Mon, 6 Jun 2005, Michel Rosien wrote: > Is it possible to pass an additional parameter to the %merge function in > glr-parsers? I don't know, and I didn't find anything in the documentation that addresses this question. > I can pass an additional parameter to the yyparse function with %parse

Re: Bison COPYING confusion

2005-06-07 Thread Aaron Jackson
On Jun 5, 2005, at 3:06 PM, Talin wrote: Greetings, I'm writing you because of some confusion about the licensing terms for Bison. In particular, my understanding is that Bison output is permitted to be incorporated into non-free programs. However, when I browse through the source distributi