Re: [CSS21] tiny typo in FLEX code

On Saturday 01 January 2011 18:55:32 Mark Meves wrote:
> likewise, one more near:
>   {badstring}             {return BAD_STRING);}
> 
> should be:
>   {badstring}             {return BAD_STRING;}

I've fixed both BAD_STRING and BAD_URI for the next publication.

I guess it was a typo that then got copy-pasted...

> 
> that is the last one i've found of this nature!
> 
> thanks!
> 
> On Fri, Dec 31, 2010 at 10:29 PM, Mark Meves <mark.meves@gmail.com> 
wrote:
> > in the page
> > 
> >   http://www.w3.org/TR/CSS21/grammar.html
> > 
> > in the section "G.2 Lexical scanner"
> > 
> > the line:
> >   at {baduri}                        {return BAD_URI);}
> > 
> > should probably read:
> >     at {baduri}                        {return BAD_URI;}
> > 
> > (note the errant trailing close paren)
> > 
> > This typo is ironic because the series of terminal symbols like
> > "baduri1" themselves indicate an opening paren with no
> > corresponding close paren but i doubt that is related!

:-)


Thanks!

Bert
-- 
  Bert Bos                                ( W 3 C ) http://www.w3.org/
  http://www.w3.org/people/bos                               W3C/ERCIM
  bert@w3.org                             2004 Rt des Lucioles / BP 93
  +33 (0)4 92 38 76 92            06902 Sophia Antipolis Cedex, France

Received on Thursday, 3 March 2011 15:32:33 UTC