>>> "Paul" == Paul Hilfinger <[EMAIL PROTECTED]> writes:
> In fact, this issue did get discussed when the GLR skeleton got
> introduced, and the language (or lack of it) is, AIR, deliberate on
> the part of the lead maintainers at the time. On consideration, I
> would prefer that the same ter
Paul Hilfinger wrote:
In fact, this issue did get discussed when the GLR skeleton got
introduced, and the language (or lack of it) is, AIR, deliberate on
the part of the lead maintainers at the time. On consideration, I
would prefer that the same terms apply to all skeletons as now apply
to the C
>>> "Sylvain" == Sylvain Schmitz <[EMAIL PROTECTED]> writes:
> Paul Hilfinger wrote:
>> In fact, this issue did get discussed when the GLR skeleton got
>> introduced, and the language (or lack of it) is, AIR, deliberate on
>> the part of the lead maintainers at the time. On consideration, I
It would simplify if the supported Bison skeleton files were distributed
under the same copyright. The unsupported skeleton files, if any, should be
put in a special place, either in the distribution, or outside it, I think.
At 12:50 -0800 2005/03/09, Paul Hilfinger wrote:
>In fact, this issue did
At 10:53 +0100 2005/03/10, Sylvain Schmitz wrote:
>Paul Hilfinger wrote:
>
>> In fact, this issue did get discussed when the GLR skeleton got
>> introduced, and the language (or lack of it) is, AIR, deliberate on
>> the part of the lead maintainers at the time. On consideration, I
>> would prefer
Please keep the cc to help-bison, so others know. When you get the right
bison installed, its version can be checked by the --version option.
At 08:42 +0100 2005/03/10, <[EMAIL PROTECTED]> wrote:
>The error where not generated by bison. When I test with "which bison" I found
that the computer use
Sylvain Schmitz <[EMAIL PROTECTED]> writes:
> It might have been true when these skeleton first appeared, but I
> don't think it is any more, since both commercial and open source
> implementations exist now.
OK, let's solve the problem. The first step: could you please come up
with a brief list
Hans Aberg <[EMAIL PROTECTED]> writes:
> the output of a copyrighted program is rarely viewed as being
> covered by the copyright of the program that made it.
No, actually it's quite common. For example, if I run the traditional
/usr/ccs/bin/yacc that is shipped with Solaris 9, the output file
y
Hello,
I'm currently trying to gain some experience with flex and bison. In one of my
projects, I'd like to use these two tools together with some Qt classes. I'm
not trying to create an object-oriented parser, I'm just using Qt's string and
list objects as I'm much more familiar with them. The i
> Hans Aberg <[EMAIL PROTECTED]> writes:
>
> > the output of a copyrighted program is rarely viewed as being
> > covered by the copyright of the program that made it.
>
> No, actually it's quite common. For example, if I run the traditional
> /usr/ccs/bin/yacc that is shipped with Solari
Paul Hilfinger <[EMAIL PROTECTED]> writes:
> Actually, I believe that the Berne convention gives no standing
> whatever to written copyright notices of this sort. Instead, if I
> produce a copyrightable work, that work is protected by copyright
> unless I take steps to make it otherwise.
Yes, th
[For some unknown reason, my email to Paul Eggert bounces.]
Paul Eggert's comment does not prove commonness :-), except perhaps in the
case of Yacc and related programs.
When I try to think about computer software in general, it always is the
principle that Paul Hilfinger indicates. If the progra
Volker Wegert wrote:
However, I get the following error message during linking (output
abbreviated):
Stupid question, but I assume that you are aware of the name mangling in
C++ and are properly externing your declarations to compensate ?
--
alfonso e. urdaneta
www.red82.com - are you ready ?
___
No, there is no such Bison design doc's: Only reading the Bison source code
itself. (Apart from that somebody wrote something in Spanish, I think.)
link ?
--
alfonso e. urdaneta
www.red82.com - are you ready ?
___
Help-bison@gnu.org http://lists.gnu.org/m
14 matches
Mail list logo
