On Fri, Jul 22, 2011 at 11:55:45AM -0700, Bakul Shah wrote: > On Fri, 22 Jul 2011 14:48:44 EDT "comeauat9f...@gmail.com" > <comeauat9f...@gmail.com> wrote: > > On Jul 22, 2011, at 2:38 PM, Bakul Shah <ba...@bitblocks.com> wrote: > > > On Fri, 22 Jul 2011 13:53:41 EDT erik quanstrom > > > <quans...@labs.coraid.com>= > > wrote: > > >> can you give am example where // comments with ' cause > > >> trouble. i can't replicate. > > >> > > >> - erik > > > > > > In 9vx: > > > > > > term% yacc go/src/cmd/gc/go.y > > > > > > fatal error:newline in string or char. const., /go/src/cmd/gc/go.y:528 > > > > > > > > > // If the last token read by the lexer was consumed > > > // as part of the case, clear it (parser has cleared yychar). > > > // If the last token read by the lexer was the lookahead > > > // leave it alone (parser has it cached in yychar). > > > ====> // This is so that the stmt_list action doesn't look at > > > // the case tokens if the stmt_list is empty. > > > yylast = yychar; > > > > pcc accepts -+ as well as cpp, perhaps a way to pass it as an environment > > and > > /or make variable? > > What does pcc have to do with this? This is a yacc problem. [Also tested > on 9atom]
I don't know either, but the yacc source doesn't explain how this error arises. Erik is right to be skeptical. ++L
