[GROOVY-1216] Scoping: precedence rules for getters / property access / field access

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 1.0-JSR-4
• Fix Version/s: 1.0
• Component/s: class generator
• Assignee: Jochen Theodorou
• Reporter: Dierk König
• Created: 23/Jan/06 05:03
• Updated: 23/Dec/06 04:27
• Resolved: 23/Dec/06 04:27

Description

> With the latest build I found the behaviour
> below but I'm not sure that this is the expected
> behaviour.
> Seems like either the getter override for properties
> has trouble or the name resolution in testZero().
> ----
> class ExplicitThisTest extends GroovyTestCase {
> @Property zero = 0
>
> def getZero()

{ return 1 }

>
> void testZero()

{ > assert 0 == zero // ? > assert 0 == this.zero // 1 ? > assert 0 == this.@zero > }

> }

I would not say it is a new scoping bug, it is a old one with new face.
This one is on my todo list. But first we should maybe make clear what
this should mean. I would say:

assert 1==zero
assert 1==this.zero
assert 0==this.@zero

bye blackdrag

---

agreed by mittie, tug, MrG

Issue Links

• relates to: GROOVY-491 Problem with dynamic name resolution