Static member names should be resolvable based on the current class #39
Labels
obsolete
Issues that involve/depend on deprecated code, such that they are not worth pursuing
type: enhancement
Issues describing an improvement to an existing feature or capability
Milestone
Perhaps easiest to show by example. Right now,
examples/java/staticfield.saw
looks like this:Since we're running the
JavaSetup
blocks in the context of a class, we should be able to do so unqualified:"sfield.StaticField.x"
becomes"StaticField.x"
or even"x"
. The first alternative more accurately reflects how static references tend to appear in the text of Java programs, but one can refer to static members totally unqualified from within the same class, so we should allow that too.Acceptance test: the following should work identically to the above script (intentionally mixing all three reference styles):
The text was updated successfully, but these errors were encountered: