Documentation bug

[Derek M Jones]

Hello,

Section 7.1 of bison.info gives an example
of how typedef names can be redefined.

For the given example (involving foo, far, lose) to
be semantically correct the subsequent definitions
need to be in a different scope, e.g.,

typedef int foo, bar, lose

   {
   static foo (bar);
   static int foo (lose);
   }

If the three lines occur in the same scope there is
a constraint violation.

derek

--
Derek M Jones                                           tel: +44 (0) 1252 520 
667
Knowledge Software Ltd                            mailto:address@hidden
Applications Standards Conformance Testing   http://www.knosof.co.uk