This is a bug in our java grammars. It does accept "primary
new" constructs where the primary is not a name such as
(a).new B() but it does not accept a.new B() and gives a
syntax error.
Note that this is not a "no definition for" error as
mentioned in the submission. These are 2 separate problems
in fact, but the syntax has
to be fixed anyway.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=176094
This is a bug in our java grammars. It does accept "primary
new" constructs where the primary is not a name such as
(a).new B() but it does not accept a.new B() and gives a
syntax error.
Note that this is not a "no definition for" error as
mentioned in the submission. These are 2 separate problems
in fact, but the syntax has
to be fixed anyway.