RE: Help-bison digest, Vol 1 #261 - 5 msgs

[Hans Aberg]

At 09:57 +0600 2002/02/15, Hareendra Pelige wrote:
>Hi Bison,
>Is there object oriented compiler generators availabale?
>
>Thanks
>Keerthi
>
>-----Original Message-----
>From: address@hidden [mailto:address@hidden
>Sent: Thursday, February 14, 2002 11:03 PM
>To: address@hidden
>Subject: Help-bison digest, Vol 1 #261 - 5 msgs
>
>
>Send Help-bison mailing list submissions to
>       address@hidden
>
>To subscribe or unsubscribe via the World Wide Web, visit
>       http://mail.gnu.org/mailman/listinfo/help-bison
>or, via email, send a message with subject or body 'help' to
>       address@hidden
>
>You can reach the person managing the list at
>       address@hidden
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of Help-bison digest..."
>
>
>Today's Topics:
>
>   1. Bison Success Stories? (Bob Wilkinson)
>   2. Re: Bison Success Stories? (Pascal Bart)
>   3. Re: Bison Success Stories? (Marc Autret)
>   4. Re: Bison Success Stories? (Akim Demaille)
>   5. Re: Bison Success Stories? (Hans Aberg)
>
>--__--__--
>
>Message: 1
>From: "Bob Wilkinson" <address@hidden>
>To: address@hidden
>Subject: Bison Success Stories?
>Date: Wed, 13 Feb 2002 18:25:59 -0500
>
>Hi,
>My company is using Bison on a project for a very particular customer.  If
>we use non-commercial software we have to somehow 'prove' that the software
>works (because if it doesn't they have no one blame, it's stupid, I know).
>The best way I can come up with to show that Bison is the reliable tool I
>know it to be is to list some commercial applications where Bison is used,
>preferably something with a safety aspect to it.
>Can anyone point me to a list of this type  (if one exists) or possibly
>provide any references?
>Thanks,
>-Bob
>
>_________________________________________________________________
>MSN Photos is the easiest way to share and print your photos:
>http://photos.msn.com/support/worldwide.aspx
>
>
>
>--__--__--
>
>Message: 2
>From: "Pascal Bart" <address@hidden>
>To: "Bob Wilkinson" <address@hidden>,
>       <address@hidden>
>Subject: Re: Bison Success Stories?
>Date: Thu, 14 Feb 2002 11:15:03 +0100
>
>Hi,
>
>> My company is using Bison on a project for a very particular customer. =
> If=20
>> we use non-commercial software we have to somehow 'prove' that the =
>software=20
>> works (because if it doesn't they have no one blame, it's stupid, I =
>know).
>> The best way I can come up with to show that Bison is the reliable =
>tool I=20
>> know it to be is to list some commercial applications where Bison is =
>used,=20
>> preferably something with a safety aspect to it.
>
>Bison is working fine, its generated parser are used in mysql, bash, =
>gcc, and more,
>but I would to remember you that Bison generated parsers are under GPL =
>license,
>so it cann't be include in a commercial application, because GPL source =
>code
>can _only_ be used in a GPL application, for more information see
>http://www.gnu.org/licenses/gpl.txt.
>
>
>
>
>
>
>
>
>--__--__--
>
>Message: 3
>To: "Pascal Bart" <address@hidden>
>Cc: "Bob Wilkinson" <address@hidden>,  <address@hidden>
>Subject: Re: Bison Success Stories?
>From: Marc Autret <address@hidden>
>Date: Thu, 14 Feb 2002 06:06:14 -0500
>
>"Pascal Bart" <address@hidden> writes:
>
>> Hi,
>>
>> > My company is using Bison on a project for a very particular customer.
>If
>> > we use non-commercial software we have to somehow 'prove' that the
>software
>> > works (because if it doesn't they have no one blame, it's stupid, I
>know).
>> > The best way I can come up with to show that Bison is the reliable tool
>I
>> > know it to be is to list some commercial applications where Bison is
>used,
>> > preferably something with a safety aspect to it.
>>
>> but I would to remember you that Bison generated parsers are under GPL
>license,
>> so it cann't be include in a commercial application, because GPL source
>code
>> can _only_ be used in a GPL application, for more information see
>
>>From bison.simple :
>
>/* As a special exception, when this file is copied by Bison into a
>   Bison output file, you may use that output file without restriction.
>   This special exception was added by the Free Software Foundation
>   in version 1.24 of Bison.  */
>
>--
>Marc Autret
>
>
>--__--__--
>
>Message: 4
>To: "Pascal Bart" <address@hidden>
>Cc: "Bob Wilkinson" <address@hidden>, <address@hidden>
>Subject: Re: Bison Success Stories?
>From: Akim Demaille <address@hidden>
>Date: Thu, 14 Feb 2002 12:08:37 +0100
>
>>>>>> "Pascal" == Pascal Bart <address@hidden> writes:
>
>Pascal> Hi,
>>> My company is using Bison on a project for a very particular
>>> customer.  If we use non-commercial software we have to somehow
>>> 'prove' that the software works (because if it doesn't they have no
>>> one blame, it's stupid, I know).  The best way I can come up with
>>> to show that Bison is the reliable tool I know it to be is to list
>>> some commercial applications where Bison is used, preferably
>>> something with a safety aspect to it.
>
>Pascal> Bison is working fine, its generated parser are used in mysql,
>Pascal> bash, gcc, and more, but I would to remember you that Bison
>Pascal> generated parsers are under GPL license, so it cann't be
>Pascal> include in a commercial application, because GPL source code
>Pascal> can _only_ be used in a GPL application, for more information
>Pascal> see http://www.gnu.org/licenses/gpl.txt.
>
>This is *wrong*.
>
>Thanks God, this is dead wrong: read the f*g license!
>
>
>bison.simple:
>
>/* As a special exception, when this file is copied by Bison into a
>   Bison output file, you may use that output file without restriction.
>   This special exception was added by the Free Software Foundation
>   in version 1.24 of Bison.  */
>
>
>
>
>bison.texi:
>
>Conditions for Using Bison
>**************************
>
>   As of Bison version 1.24, we have changed the distribution terms for
>`yyparse' to permit using Bison's output in nonfree programs.
>Formerly, Bison parsers could be used only in programs that were free
>software.
>
>   The other GNU programming tools, such as the GNU C compiler, have
>never had such a requirement.  They could always be used for nonfree
>software.  The reason Bison was different was not due to a special
>policy decision; it resulted from applying the usual General Public
>License to all of the Bison source code.
>
>   The output of the Bison utility--the Bison parser file--contains a
>verbatim copy of a sizable piece of Bison, which is the code for the
>`yyparse' function.  (The actions from your grammar are inserted into
>this function at one point, but the rest of the function is not
>changed.)  When we applied the GPL terms to the code for `yyparse', the
>effect was to restrict the use of Bison output to free software.
>
>   We didn't change the terms because of sympathy for people who want to
>make software proprietary.  *Software should be free.*  But we
>concluded that limiting Bison's use to free software was doing little to
>encourage people to make other software free.  So we decided to make the
>practical conditions for using Bison match the practical conditions for
>using the other GNU tools.
>
>
>
>Now, to answer the question, I'd submit the following paragraph.
>
>What is Bison
>=============
>
>   Yacc is a generator of efficient parsers.  A "parser" is a program
>or routine which recognizes the structure of sentences.  Yacc's input is
>composed of "rules" with associated actions.  The rules must be
>"context free", i.e., their left hand side is composed of a single
>nonterminal symbol, and their right hand side is composed of series of
>terminal and nonterminal symbols.  When a rule is reduced, the
>associated C code is triggered.
>
>   Yacc is based on pushdown automata.  It is a implementation of the
>LALR(1) parsing algorithm, which is sufficient for most programming
>languages, but can be too limited a framework to describe conveniently
>intricate languages.
>
>   Yacc, and all its declinations (CAMLYacc for CAML etc.) are used in
>numerous applications, especially compilers and interpreters.  Hence its
>name: Yet Another Compiler Compiler.
>
>
>   Bison is a free software implementation of Yacc, as described by the
>POSIX standard.  It provides a wide set of additional options and
>features, produces self contained portable code (no library is
>required), supports a more pleasant syntax, and stands as a standard of
>its own.  Since most Yacc do have problems (inter-Yacc compatibility and
>actual bugs), all the reasons are in favor of using exclusively Bison:
>the portable C code it produces can be shipped in the package and will
>compile cleanly on the user's machine.  It imposes no restriction on the
>license of the produced parser.
>
>   It is used by the GNU Compiler Collection for C, C++(1), the C
>preprocessor.  Many other programming language tools use Bison or Yacc:
>GNU AWK, Perl, but it proves itself useful in reading structured files:
>a2ps uses it to parse its style sheets.  It also helps decoding some
>limited forms of natural language: numerous GNU utilities use a Yacc
>grammar to decode dates such as `2 days ago', `3 months 1 day', `25
>Dec', `1970-01-01 00:00:01 UTC +5 hours' etc.
>
>   GNU Gettext deserves a special mention with three different uses:
>one to parse its input files, another one to parse the special comments
>in these files, and one to evaluate the foreign language dependent rules
>defining the plural forms.
>
>
>--__--__--
>
>Message: 5
>Date: Thu, 14 Feb 2002 11:29:41 +0100
>To: "Bob Wilkinson" <address@hidden>
>From: Hans Aberg <address@hidden>
>Subject: Re: Bison Success Stories?
>Cc: address@hidden
>
>At 18:25 -0500 2002/02/13, Bob Wilkinson wrote:
>>My company is using Bison on a project for a very particular customer.  If
>>we use non-commercial software we have to somehow 'prove' that the software
>>works (because if it doesn't they have no one blame, it's stupid, I know).
>
>Sure, they have, they can blame themselves. :-)
>
>By the way, if it didn't work, what would your company want, a refund? -- I
>mean, I really don't know any commercial software company that gives any
>other guarantees of their software.
>
>  Hans Aberg
>
>
>
>
>
>--__--__--
>
>_______________________________________________
>Help-bison mailing list
>address@hidden
>http://mail.gnu.org/mailman/listinfo/help-bison
>
>
>End of Help-bison Digest
>
>_______________________________________________
>Help-bison mailing list
>address@hidden
>http://mail.gnu.org/mailman/listinfo/help-bison

Do you want the perser generater or its generated parsers to be OO?

  Hans Aberg