|Help with Yacc reduce/reduce conflict email@example.com (Warren) (2010-06-21)|
|Re: Help with Yacc reduce/reduce conflict firstname.lastname@example.org (glen herrmannsfeldt) (2010-06-23)|
|Re: Help with Yacc reduce/reduce conflict email@example.com (russell kym horsell) (2010-06-24)|
|Re: Help with Yacc reduce/reduce conflict firstname.lastname@example.org (Paul Mann) (2010-07-01)|
|From:||glen herrmannsfeldt <email@example.com>|
|Date:||Wed, 23 Jun 2010 18:25:34 +0000 (UTC)|
|Organization:||Aioe.org NNTP Server|
|Posted-Date:||25 Jun 2010 16:24:20 EDT|
Warren <firstname.lastname@example.org> wrote:
> I'm writing a tool for novice Java students to submit their programs
> on-line and get back warnings about common mistakes, e.g. if (x = y),
> and assignments where the == operator is used instead of =.
I thought that Java made this C mistake illegal, except in
the case of boolean variables, with the requirement that the
expression be of type boolean.
Though I do like the simplicity of the C form, it is a convenient
source of hard to find bugs.
It might be that the compilers don't give an instructive
error for this case, though.
Return to the
Search the comp.compilers archives again.