This is bovine.info, produced by makeinfo version 4.3 from bovine.texi.

This manual documents Bovine parser development in Semantic

   Copyright (C) 1999, 2000, 2001, 2002, 2003, 2004 Eric M. Ludlam
Copyright (C) 2001, 2002, 2003, 2004 David Ponce Copyright (C) 2002,
2003 Richard Y. Kim

     Permission is granted to copy, distribute and/or modify this
     document under the terms of the GNU Free Documentation License,
     Version 1.1 or any later version published by the Free Software
     Foundation; with the Invariant Sections being list their titles,
     with the Front-Cover Texts being list, and with the Back-Cover
     Texts being list.  A copy of the license is included in the
     section entitled "GNU Free Documentation License".
   
INFO-DIR-SECTION Emacs
START-INFO-DIR-ENTRY
* Semantic bovine parser development: (bovine).
END-INFO-DIR-ENTRY

   This file documents parser development with the bovine parser
generator _Infrastructure for parser based text analysis in Emacs_

   Copyright (C) 1999, 2000, 2001, 2002, 2003, 2004 Eric M. Ludlam,
David Ponce, and Richard Y. Kim


File: bovine.info,  Node: Top,  Next: Starting Rules,  Up: (dir)

Bovine parser development
*************************

The "bovine" parser is the original semantic parser, and is an
implementation of an LL parser.  It is good for simple languages.  It
has many conveniences making grammar writing easy.  The conveniences
make it less powerful than a Bison-like LALR parser.  For more
information, *note the Wisent Parser Manual: (wisent)top.

Bovine LL grammars are stored in files with a `.by' extension.  When
compiled, the contents is converted into a file of the form
`NAME-by.el'.  This, in turn is byte compiled.  *note Grammar Framework
Manual: (grammar-fw)top.

* Menu:

* Starting Rules::              The starting rules for the grammar.
* Bovine Grammar Rules::        Rules used to parse a language
* Optional Lambda Expression::  Actions to take when a rule is matched
* Bovine Examples::             Simple Samples
* GNU Free Documentation License::
* Index::


File: bovine.info,  Node: Starting Rules,  Next: Bovine Grammar Rules,  Prev: Top,  Up: Top

Starting Rules
**************

In Bison, one and only one nonterminal is designated as the "start"
symbol.  In semantic, one or more nonterminals can be designated as the
"start" symbol.  They are declared following the `%start' keyword
separated by spaces.  *note (grammar-fw)start Decl::.

If no `%start' keyword is used in a grammar, then the very first is
used.  Internally the first start nonterminal is targeted by the
reserved symbol `bovine-toplevel', so it can be found by the parser
harness.

To find locally defined variables, the local context handler needs to
parse the body of functional code.  The `scopestart' declaration
specifies the name of a nonterminal used as the goal to parse a local
context, *note (grammar-fw)scopestart Decl::.  Internally the
scopestart nonterminal is targeted by the reserved symbol
`bovine-inner-scope', so it can be found by the parser harness.


File: bovine.info,  Node: Bovine Grammar Rules,  Next: Optional Lambda Expression,  Prev: Starting Rules,  Up: Top

Bovine Grammar Rules
********************

The rules are what allow the compiler to create tags from a language
file.  Once the setup is done in the prologue, you can start writing
rules.  *note (grammar-fw)Grammar Rules::.

     RESULT : COMPONENTS1 OPTIONAL-SEMANTIC-ACTION1)
            | COMPONENTS2 OPTIONAL-SEMANTIC-ACTION2
            ;

RESULT is a nonterminal, that is a symbol synthesized in your grammar.
COMPONENTS is a list of elements that are to be matched if RESULT is to
be made.  OPTIONAL-SEMANTIC-ACTION is an optional sequence of
simplified Emacs Lisp expressions for concocting the parse tree.

In bison, each time an element of COMPONENTS is found, it is "shifted"
onto the parser stack.  (The stack of matched elements.)  When all
COMPONENTS' elements have been matched, it is "reduced" to RESULT.
*Note (bison)Algorithm::.

A particular RESULT written into your grammar becomes the parser's
goal.  It is designated by a `%start' statement (*note Starting
Rules::).  The value returned by the associated
OPTIONAL-SEMANTIC-ACTION is the parser's result.  It should be a tree
of semantic "tags", *note (semantic-appdev)Semantic Tags::.

COMPONENTS is made up of symbols.  A symbol such as `FOO' means that a
syntactic token of class `FOO' must be matched.

* Menu:

* How Lexical Tokens Match::
* Grammar-to-Lisp Details::
* Order of components in rules::


File: bovine.info,  Node: How Lexical Tokens Match,  Next: Grammar-to-Lisp Details,  Up: Bovine Grammar Rules

How Lexical Tokens Match
========================

A lexical rule must be used to define how to match a lexical token.

For instance:

     %keyword FOO "foo"

Means that `FOO' is a reserved language keyword, matched as such by
looking up into a keyword table, *note (grammar-fw)keyword Decl::.
This is because `"foo"' will be converted to `FOO' in the lexical
analysis stage.  Thus the symbol `FOO' won't be available any other way.

If we specify our token in this way:

     %token <symbol> FOO "foo"

then `FOO' will match the string `"foo"' explicitly, but it won't do so
at the lexical level, allowing use of the text `"foo"' in other forms
of regular expressions.

In that case, `FOO' is a `symbol'-type token.  To match, a `symbol'
must first be encountered, and then it must `string-match "foo"'.

*Caution:*
     Be especially careful to remember that `"foo"', and more generally
     the %token's match-value string, is a regular expression!

Non symbol tokens are also allowed.  For example:

     %token <punctuation> PERIOD "[.]"
     
     filename : symbol PERIOD symbol
              ;

`PERIOD' is a `punctuation'-type token that will explicitly match one
period when used in the above rule.

*Please Note:*
     `symbol', `punctuation', etc., are predefined lexical token types,
     based on the "syntax class"-character associations currently in
     effect.


File: bovine.info,  Node: Grammar-to-Lisp Details,  Next: Order of components in rules,  Prev: How Lexical Tokens Match,  Up: Bovine Grammar Rules

Grammar-to-Lisp Details
=======================

For the bovinator, lexical token matching patterns are _inlined_.  When
the grammar-to-lisp converter encounters a lexical token declaration of
the form:

     %token <TYPE> TOKEN-NAME MATCH-VALUE

It substitutes every occurrences of TOKEN-NAME in rules, by its
expanded form:

     TYPE MATCH-VALUE

For example:

     %token <symbol> MOOSE "moose"
     
     find_a_moose: MOOSE
                 ;

Will generate this pseudo equivalent-rule:

     find_a_moose: symbol "moose"   ;; invalid syntax!
                 ;

Thus, from the bovinator point of view, the COMPONENTS part of a rule
is made up of symbols and strings.  A string in the mix means that the
previous symbol must have the additional constraint of exactly matching
it, as described in *Note How Lexical Tokens Match::.

*Please Note:*
     For the bovinator, this task was mixed into the language
     definition to simplify implementation, though Bison's technique is
     more efficient.


File: bovine.info,  Node: Order of components in rules,  Prev: Grammar-to-Lisp Details,  Up: Bovine Grammar Rules

Order of components in rules
============================

If a rule has multiple components, order is important, for example

     headerfile : symbol PERIOD symbol
                | symbol
                ;

would match `foo.h' or the C++ header `foo'.  The bovine parser will
first attempt to match the long form, and then the short form.  If they
were in reverse order, then the long form would never be tested.


File: bovine.info,  Node: Optional Lambda Expression,  Next: Bovine Examples,  Prev: Bovine Grammar Rules,  Up: Top

Optional Lambda Expressions
***************************

The OLE ("Optional Lambda Expression") is converted into a bovine
lambda.  This lambda has special short-cuts to simplify reading the
semantic action definition.  An OLE like this:

     ( $1 )

results in a lambda return which consists entirely of the string or
object found by matching the first (zeroth) element of match.  An OLE
like this:

     ( ,(foo $1) )

executes `foo' on the first argument, and then splices its return into
the return list whereas:

     ( (foo $1) )

executes `foo', and that is placed in the return list.

Here are other things that can appear inline:

`$1'
     The first object matched.

`,$1'
     The first object spliced into the list (assuming it is a list from
     a non-terminal).

`'$1'
     The first object matched, placed in a list.  i.e. `( $1 )'.

`foo'
     The symbol `foo' (exactly as displayed).

`(foo)'
     A function call to foo which is stuck into the return list.

`,(foo)'
     A function call to foo which is spliced into the return list.

`'(foo)'
     A function call to foo which is stuck into the return list in a
     list.

`(EXPAND $1 NONTERMINAL DEPTH)'
     A list starting with `EXPAND' performs a recursive parse on the
     token passed to it (represented by `$1' above.)  The "semantic
     list" is a common token to expand, as there are often interesting
     things in the list.  The NONTERMINAL is a symbol in your table
     which the bovinator will start with when parsing.  NONTERMINAL's
     definition is the same as any other nonterminal.  DEPTH should be
     at least `1' when descending into a semantic list.

`(EXPANDFULL $1 NONTERMINAL DEPTH)'
     Is like `EXPAND', except that the parser will iterate over
     NONTERMINAL until there are no more matches.  (The same way the
     parser iterates over the starting rule (*note Starting Rules::).
     This lets you have much simpler rules in this specific case, and
     also lets you have positional information in the returned tokens,
     and error skipping.

`(ASSOC SYMBOL1 VALUE1 SYMBOL2 VALUE2 ...)'
     This is used for creating an association list.  Each SYMBOL is
     included in the list if the associated VALUE is non-`nil'.  While
     the items are all listed explicitly, the created structure is an
     association list of the form:

          ((SYMBOL1 . VALUE1) (SYMBOL2 . VALUE2) ...)

`(TAG NAME CLASS [ATTRIBUTES])'
     This creates one tag in the current buffer.

    NAME
          Is a string that represents the tag in the language.

    CLASS
          Is the kind of tag being create, such as `function', or
          `variable', though any symbol will work.

    ATTRIBUTES
          Is an optional set of labeled values such as
          `:constant-flag t :parent "parenttype"'.

`(TAG-VARIABLE NAME TYPE DEFAULT-VALUE [ATTRIBUTES])'
`(TAG-FUNCTION NAME TYPE ARG-LIST [ATTRIBUTES])'
`(TAG-TYPE NAME TYPE MEMBERS PARENTS [ATTRIBUTES])'
`(TAG-INCLUDE NAME SYSTEM-FLAG [ATTRIBUTES])'
`(TAG-PACKAGE NAME DETAIL [ATTRIBUTES])'
`(TAG-CODE NAME DETAIL [ATTRIBUTES])'
     Create a tag with NAME of respectively the class `variable',
     `function', `type', `include', `package', and `code'.  See *note
     (semantic-appdev)Creating Tags:: for the lisp functions these
     translate into.

If the symbol `%quotemode backquote' is specified, then use `,@' to
splice a list in, and `,' to evaluate the expression.  This lets you
send `$1' as a symbol into a list instead of having it expanded inline.


File: bovine.info,  Node: Bovine Examples,  Next: GNU Free Documentation License,  Prev: Optional Lambda Expression,  Up: Top

Examples
********

The rule:

     any-symbol: symbol
               ;

is equivalent to

     any-symbol: symbol
                 ( $1 )
               ;

which, if it matched the string `"A"', would return

     ( "A" )

If this rule were used like this:

     %token <punctuation> EQUAL "="
     ...
     assign: any-symbol EQUAL any-symbol
             ( $1 $3 )
           ;

it would match `"A=B"', and return

     ( ("A") ("B") )

The letters `A' and `B' come back in lists because `any-symbol' is a
nonterminal, not an actual lexical element.

To get a better result with nonterminals, use , to splice lists in like
this:

     %token <punctuation> EQUAL "="
     ...
     assign: any-symbol EQUAL any-symbol
             ( ,$1 ,$3 )
           ;

which would return

     ( "A" "B" )


File: bovine.info,  Node: GNU Free Documentation License,  Next: Index,  Prev: Bovine Examples,  Up: Top

GNU Free Documentation License
******************************

                        Version 1.1, March 2000
     Copyright (C) 2000  Free Software Foundation, Inc.
     59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
     
     Everyone is permitted to copy and distribute verbatim copies
     of this license document, but changing it is not allowed.


  0. PREAMBLE

     The purpose of this License is to make a manual, textbook, or other
     written document "free" in the sense of freedom: to assure everyone
     the effective freedom to copy and redistribute it, with or without
     modifying it, either commercially or noncommercially.  Secondarily,
     this License preserves for the author and publisher a way to get
     credit for their work, while not being considered responsible for
     modifications made by others.

     This License is a kind of "copyleft", which means that derivative
     works of the document must themselves be free in the same sense.
     It complements the GNU General Public License, which is a copyleft
     license designed for free software.

     We have designed this License in order to use it for manuals for
     free software, because free software needs free documentation: a
     free program should come with manuals providing the same freedoms
     that the software does.  But this License is not limited to
     software manuals; it can be used for any textual work, regardless
     of subject matter or whether it is published as a printed book.
     We recommend this License principally for works whose purpose is
     instruction or reference.


  1. APPLICABILITY AND DEFINITIONS

     This License applies to any manual or other work that contains a
     notice placed by the copyright holder saying it can be distributed
     under the terms of this License.  The "Document", below, refers to
     any such manual or work.  Any member of the public is a licensee,
     and is addressed as "you".

     A "Modified Version" of the Document means any work containing the
     Document or a portion of it, either copied verbatim, or with
     modifications and/or translated into another language.

     A "Secondary Section" is a named appendix or a front-matter
     section of the Document that deals exclusively with the
     relationship of the publishers or authors of the Document to the
     Document's overall subject (or to related matters) and contains
     nothing that could fall directly within that overall subject.
     (For example, if the Document is in part a textbook of
     mathematics, a Secondary Section may not explain any mathematics.)
     The relationship could be a matter of historical connection with
     the subject or with related matters, or of legal, commercial,
     philosophical, ethical or political position regarding them.

     The "Invariant Sections" are certain Secondary Sections whose
     titles are designated, as being those of Invariant Sections, in
     the notice that says that the Document is released under this
     License.

     The "Cover Texts" are certain short passages of text that are
     listed, as Front-Cover Texts or Back-Cover Texts, in the notice
     that says that the Document is released under this License.

     A "Transparent" copy of the Document means a machine-readable copy,
     represented in a format whose specification is available to the
     general public, whose contents can be viewed and edited directly
     and straightforwardly with generic text editors or (for images
     composed of pixels) generic paint programs or (for drawings) some
     widely available drawing editor, and that is suitable for input to
     text formatters or for automatic translation to a variety of
     formats suitable for input to text formatters.  A copy made in an
     otherwise Transparent file format whose markup has been designed
     to thwart or discourage subsequent modification by readers is not
     Transparent.  A copy that is not "Transparent" is called "Opaque".

     Examples of suitable formats for Transparent copies include plain
     ASCII without markup, Texinfo input format, LaTeX input format,
     SGML or XML using a publicly available DTD, and
     standard-conforming simple HTML designed for human modification.
     Opaque formats include PostScript, PDF, proprietary formats that
     can be read and edited only by proprietary word processors, SGML
     or XML for which the DTD and/or processing tools are not generally
     available, and the machine-generated HTML produced by some word
     processors for output purposes only.

     The "Title Page" means, for a printed book, the title page itself,
     plus such following pages as are needed to hold, legibly, the
     material this License requires to appear in the title page.  For
     works in formats which do not have any title page as such, "Title
     Page" means the text near the most prominent appearance of the
     work's title, preceding the beginning of the body of the text.

  2. VERBATIM COPYING

     You may copy and distribute the Document in any medium, either
     commercially or noncommercially, provided that this License, the
     copyright notices, and the license notice saying this License
     applies to the Document are reproduced in all copies, and that you
     add no other conditions whatsoever to those of this License.  You
     may not use technical measures to obstruct or control the reading
     or further copying of the copies you make or distribute.  However,
     you may accept compensation in exchange for copies.  If you
     distribute a large enough number of copies you must also follow
     the conditions in section 3.

     You may also lend copies, under the same conditions stated above,
     and you may publicly display copies.

  3. COPYING IN QUANTITY

     If you publish printed copies of the Document numbering more than
     100, and the Document's license notice requires Cover Texts, you
     must enclose the copies in covers that carry, clearly and legibly,
     all these Cover Texts: Front-Cover Texts on the front cover, and
     Back-Cover Texts on the back cover.  Both covers must also clearly
     and legibly identify you as the publisher of these copies.  The
     front cover must present the full title with all words of the
     title equally prominent and visible.  You may add other material
     on the covers in addition.  Copying with changes limited to the
     covers, as long as they preserve the title of the Document and
     satisfy these conditions, can be treated as verbatim copying in
     other respects.

     If the required texts for either cover are too voluminous to fit
     legibly, you should put the first ones listed (as many as fit
     reasonably) on the actual cover, and continue the rest onto
     adjacent pages.

     If you publish or distribute Opaque copies of the Document
     numbering more than 100, you must either include a
     machine-readable Transparent copy along with each Opaque copy, or
     state in or with each Opaque copy a publicly-accessible
     computer-network location containing a complete Transparent copy
     of the Document, free of added material, which the general
     network-using public has access to download anonymously at no
     charge using public-standard network protocols.  If you use the
     latter option, you must take reasonably prudent steps, when you
     begin distribution of Opaque copies in quantity, to ensure that
     this Transparent copy will remain thus accessible at the stated
     location until at least one year after the last time you
     distribute an Opaque copy (directly or through your agents or
     retailers) of that edition to the public.

     It is requested, but not required, that you contact the authors of
     the Document well before redistributing any large number of
     copies, to give them a chance to provide you with an updated
     version of the Document.

  4. MODIFICATIONS

     You may copy and distribute a Modified Version of the Document
     under the conditions of sections 2 and 3 above, provided that you
     release the Modified Version under precisely this License, with
     the Modified Version filling the role of the Document, thus
     licensing distribution and modification of the Modified Version to
     whoever possesses a copy of it.  In addition, you must do these
     things in the Modified Version:

     A. Use in the Title Page (and on the covers, if any) a title
     distinct    from that of the Document, and from those of previous
     versions    (which should, if there were any, be listed in the
     History section    of the Document).  You may use the same title
     as a previous version    if the original publisher of that version
     gives permission.
     B. List on the Title Page, as authors, one or more persons or
     entities    responsible for authorship of the modifications in the
     Modified    Version, together with at least five of the principal
     authors of the    Document (all of its principal authors, if it
     has less than five).
     C. State on the Title page the name of the publisher of the
     Modified Version, as the publisher.
     D. Preserve all the copyright notices of the Document.
     E. Add an appropriate copyright notice for your modifications
     adjacent to the other copyright notices.
     F. Include, immediately after the copyright notices, a license
     notice    giving the public permission to use the Modified Version
     under the    terms of this License, in the form shown in the
     Addendum below.
     G. Preserve in that license notice the full lists of Invariant
     Sections    and required Cover Texts given in the Document's
     license notice.
     H. Include an unaltered copy of this License.
     I. Preserve the section entitled "History", and its title, and add
     to    it an item stating at least the title, year, new authors, and
       publisher of the Modified Version as given on the Title Page.
     If    there is no section entitled "History" in the Document,
     create one    stating the title, year, authors, and publisher of
     the Document as    given on its Title Page, then add an item
     describing the Modified    Version as stated in the previous
     sentence.
     J. Preserve the network location, if any, given in the Document for
       public access to a Transparent copy of the Document, and
     likewise    the network locations given in the Document for
     previous versions    it was based on.  These may be placed in the
     "History" section.     You may omit a network location for a work
     that was published at    least four years before the Document
     itself, or if the original    publisher of the version it refers
     to gives permission.
     K. In any section entitled "Acknowledgements" or "Dedications",
     preserve the section's title, and preserve in the section all the
      substance and tone of each of the contributor acknowledgements
     and/or dedications given therein.
     L. Preserve all the Invariant Sections of the Document,
     unaltered in their text and in their titles.  Section numbers
     or the equivalent are not considered part of the section titles.
     M. Delete any section entitled "Endorsements".  Such a section
     may not be included in the Modified Version.
     N. Do not retitle any existing section as "Endorsements"    or to
     conflict in title with any Invariant Section.

     If the Modified Version includes new front-matter sections or
     appendices that qualify as Secondary Sections and contain no
     material copied from the Document, you may at your option
     designate some or all of these sections as invariant.  To do this,
     add their titles to the list of Invariant Sections in the Modified
     Version's license notice.  These titles must be distinct from any
     other section titles.

     You may add a section entitled "Endorsements", provided it contains
     nothing but endorsements of your Modified Version by various
     parties-for example, statements of peer review or that the text has
     been approved by an organization as the authoritative definition
     of a standard.

     You may add a passage of up to five words as a Front-Cover Text,
     and a passage of up to 25 words as a Back-Cover Text, to the end
     of the list of Cover Texts in the Modified Version.  Only one
     passage of Front-Cover Text and one of Back-Cover Text may be
     added by (or through arrangements made by) any one entity.  If the
     Document already includes a cover text for the same cover,
     previously added by you or by arrangement made by the same entity
     you are acting on behalf of, you may not add another; but you may
     replace the old one, on explicit permission from the previous
     publisher that added the old one.

     The author(s) and publisher(s) of the Document do not by this
     License give permission to use their names for publicity for or to
     assert or imply endorsement of any Modified Version.

  5. COMBINING DOCUMENTS

     You may combine the Document with other documents released under
     this License, under the terms defined in section 4 above for
     modified versions, provided that you include in the combination
     all of the Invariant Sections of all of the original documents,
     unmodified, and list them all as Invariant Sections of your
     combined work in its license notice.

     The combined work need only contain one copy of this License, and
     multiple identical Invariant Sections may be replaced with a single
     copy.  If there are multiple Invariant Sections with the same name
     but different contents, make the title of each such section unique
     by adding at the end of it, in parentheses, the name of the
     original author or publisher of that section if known, or else a
     unique number.  Make the same adjustment to the section titles in
     the list of Invariant Sections in the license notice of the
     combined work.

     In the combination, you must combine any sections entitled
     "History" in the various original documents, forming one section
     entitled "History"; likewise combine any sections entitled
     "Acknowledgements", and any sections entitled "Dedications".  You
     must delete all sections entitled "Endorsements."

  6. COLLECTIONS OF DOCUMENTS

     You may make a collection consisting of the Document and other
     documents released under this License, and replace the individual
     copies of this License in the various documents with a single copy
     that is included in the collection, provided that you follow the
     rules of this License for verbatim copying of each of the
     documents in all other respects.

     You may extract a single document from such a collection, and
     distribute it individually under this License, provided you insert
     a copy of this License into the extracted document, and follow
     this License in all other respects regarding verbatim copying of
     that document.

  7. AGGREGATION WITH INDEPENDENT WORKS

     A compilation of the Document or its derivatives with other
     separate and independent documents or works, in or on a volume of
     a storage or distribution medium, does not as a whole count as a
     Modified Version of the Document, provided no compilation
     copyright is claimed for the compilation.  Such a compilation is
     called an "aggregate", and this License does not apply to the
     other self-contained works thus compiled with the Document, on
     account of their being thus compiled, if they are not themselves
     derivative works of the Document.

     If the Cover Text requirement of section 3 is applicable to these
     copies of the Document, then if the Document is less than one
     quarter of the entire aggregate, the Document's Cover Texts may be
     placed on covers that surround only the Document within the
     aggregate.  Otherwise they must appear on covers around the whole
     aggregate.

  8. TRANSLATION

     Translation is considered a kind of modification, so you may
     distribute translations of the Document under the terms of section
     4.  Replacing Invariant Sections with translations requires special
     permission from their copyright holders, but you may include
     translations of some or all Invariant Sections in addition to the
     original versions of these Invariant Sections.  You may include a
     translation of this License provided that you also include the
     original English version of this License.  In case of a
     disagreement between the translation and the original English
     version of this License, the original English version will prevail.

  9. TERMINATION

     You may not copy, modify, sublicense, or distribute the Document
     except as expressly provided for under this License.  Any other
     attempt to copy, modify, sublicense or distribute the Document is
     void, and will automatically terminate your rights under this
     License.  However, parties who have received copies, or rights,
     from you under this License will not have their licenses
     terminated so long as such parties remain in full compliance.

 10. FUTURE REVISIONS OF THIS LICENSE

     The Free Software Foundation may publish new, revised versions of
     the GNU Free Documentation License from time to time.  Such new
     versions will be similar in spirit to the present version, but may
     differ in detail to address new problems or concerns.  See
     http://www.gnu.org/copyleft/.

     Each version of the License is given a distinguishing version
     number.  If the Document specifies that a particular numbered
     version of this License "or any later version" applies to it, you
     have the option of following the terms and conditions either of
     that specified version or of any later version that has been
     published (not as a draft) by the Free Software Foundation.  If
     the Document does not specify a version number of this License,
     you may choose any version ever published (not as a draft) by the
     Free Software Foundation.


ADDENDUM: How to use this License for your documents
====================================================

To use this License in a document you have written, include a copy of
the License in the document and put the following copyright and license
notices just after the title page:


       Copyright (C)  YEAR  YOUR NAME.
       Permission is granted to copy, distribute and/or modify this document
       under the terms of the GNU Free Documentation License, Version 1.1
       or any later version published by the Free Software Foundation;
       with the Invariant Sections being LIST THEIR TITLES, with the
       Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
       A copy of the license is included in the section entitled ``GNU
       Free Documentation License''.
If you have no Invariant Sections, write "with no Invariant
Sections" instead of saying which ones are invariant.  If you have no
Front-Cover Texts, write "no Front-Cover Texts" instead of "Front-Cover
Texts being LIST"; likewise for Back-Cover Texts.

If your document contains nontrivial examples of program code, we
recommend releasing these examples in parallel under your choice of
free software license, such as the GNU General Public License, to
permit their use in free software.


File: bovine.info,  Node: Index,  Prev: GNU Free Documentation License,  Up: Top

Index
*****

* Menu:


Tag Table:
Node: Top1104
Node: Starting Rules2080
Node: Bovine Grammar Rules3068
Node: How Lexical Tokens Match4564
Node: Grammar-to-Lisp Details6058
Node: Order of components in rules7216
Node: Optional Lambda Expression7750
Node: Bovine Examples11390
Node: GNU Free Documentation License12314
Node: Index32028

End Tag Table
