[jira] [Created] (GROOVY-9851) Private field and method use from subclass is inconsistent

["Eric Milles (Jira)" <ji...@apache.org>]

Eric Milles created GROOVY-9851:
-----------------------------------

             Summary: Private field and method use from subclass is inconsistent
                 Key: GROOVY-9851
                 URL: https://issues.apache.org/jira/browse/GROOVY-9851
             Project: Groovy
          Issue Type: Bug
    Affects Versions: 2.4.16
            Reporter: Eric Milles
            Assignee: Eric Milles
             Fix For: 4.0.0-alpha-1, 3.0.5, 2.5.13


This is probably just a slice of GROOVY-1591, GROOVY-3010, GROOVY-3142, GROOVY-5438, et al. Adding {{super.}} qualifier causes strange behaviors. Please consider the following:
{code:java}
class Foo {
  private String field = 'field'
  private String method() { 'method' }
}
class Bar extends Foo {
  def baz() {
    field // MissingPropertyException: No such property: field for class: Bar
    method() // MissingMethodException: No signature of method: Bar.method()
    this.field // MissingPropertyException: No such property: field for class: Bar
    this.method() // MissingMethodException: No signature of method: Bar.method()

    // so far, so good -- although Groovy allows access to private fields and methods from outside of Bar and Foo

    super.field // MissingMethodException: No signature of method: Bar.getField() -- that's strange
    super.method() // returns "method" -- Why is this okay?

    super.@field // MissingMethodException: No signature of method: Bar.getField() -- that's strange
    super.&method // returns MethodClosure that throws NPE when called:
    (super.&method)() // NullPointerException: Cannot invoke method call() on null object-- If super.method() works, why doesn't this?
  }
}
{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)