On Sun, 1 Aug 2010, Joel E. Denny wrote: > Now thinking beyond 2.4.3, the only specific case of -Werror not working > that was mentioned on comp.compilers is the case of R/R conflicts. Bison > currently does not label R/R conflict messages as warnings, so it is not > as clear in this case that -Werror should have any effect. Would treating > parser conflicts as warnings be too contrary to traditional yacc/bison > thinking? Besides, bison already supports %error and %error-rr to turn > them into errors.
Sorry, I meant %expect and %expect-rr. > On the other hand, it seems that any diagnostic printed > on stderr is at least a warning, and I can see how the user might > appreciate a guarantee that -Werror will prevent him from missing any such > diagnostic. That seems to be the thinking at comp.compilers. Opinions?
