CEDET

Here is a small patch to wisent.texi for some of the sections I've
read so far.

Eric
------------
*** wisent.texi.~1.16.~	Sun Jun 30 10:48:01 2002
--- wisent.texi	Sun Jun 30 10:54:37 2002
***************
*** 1838,1851 ****
  @subsection Bison style
  
  @cindex Grammar Bison style
! What we call the @dfn{Bison style} is actually the traditional style
! of Bison's grammars.  Compared to bovine style, it is not
! straightforward to use grammars written in Bison style in Semantic.
! Mainly because such grammars are designed to parse the whole input
! data in one pass, and don't use the bovinator back-end mechanism
! (@pxref{Bovine style}).  With Bison style the parser is called once to
! parse the grammar start nonterminal.
! @br{}
  The following example is a snippet of the Bison style Java grammar
  provided in the Semantic distribution in the file
  @file{wisent-java.wy}.
--- 1838,1851 ----
  @subsection Bison style
  
  @cindex Grammar Bison style
! What we call the @dfn{Bison style} is the traditional style of Bison's
! grammars.  Compared to bovine style, it is not straightforward to use
! grammars written in Bison style in Semantic.  Mainly because such
! grammars are designed to parse the whole input data in one pass, and
! don't use the bovinator back-end mechanism (@pxref{Bovine style}).
! With Bison style the parser is called once to parse the grammar start
! nonterminal.
! 
  The following example is a snippet of the Bison style Java grammar
  provided in the Semantic distribution in the file
  @file{wisent-java.wy}.
***************
*** 1875,1883 ****
  unexpected input data.
  @br{}
  The second consequence is that the bovinator can't do automatic raw to
! cooked token translation, excepted for the start nonterminal value.
! So it is also necessary to explicitly return cooked semantic tokens
! from concerned semantic actions by calling the function
  @code{wisent-cooked-token} with the appropriate parameters.@*
  @xref{Start nonterminals}, for partial re-parse considerations.
  @br{}
--- 1875,1883 ----
  unexpected input data.
  @br{}
  The second consequence is that the bovinator can't do automatic raw to
! cooked token translation, except for the start nonterminal value.  It
! is necessary to explicitly return cooked semantic tokens from
! concerned semantic actions by calling the function
  @code{wisent-cooked-token} with the appropriate parameters.@*
  @xref{Start nonterminals}, for partial re-parse considerations.
  @br{}
***************
*** 1974,1979 ****
--- 1974,1982 ----
  In such cases, when it is difficult for Emacs to obtain
  @code{semantic-list} syntactic tokens, the best solution is to use
  traditional Bison style with error recovery!
+ 
+ In some extreme cases, it can also be convenient to extend
+ @dfn{semantic-flex}.  @ref{Wisent Flex}
  
  @node Start nonterminals
  @subsection Start nonterminals

-- 
          Eric Ludlam:                 zappo@..., eric@...
   Home: http://www.ultranet.com/~zappo            Siege: http://www.siege-engine.com
Emacs: http://cedet.sourceforge.net               GNU: http://www.gnu.org