Private inheritance bug: Closure accessing private method

Details

Type: Sub-task
Status: Open
Priority: Major
Resolution: Unresolved
Affects Version/s: 1.5.6
Fix Version/s: None
Component/s: class generator
Labels:
None
Environment:
Windows XP SP 2
Eclipse 3.3 & groovy-all-1.5.6.jar

Number of attachments :
0

Description

Even the inheritance is correct - the following sample returns a:

Exception in thread "main" groovy.lang.MissingMethodException: No signature of method: test.Child.parentMethodB() is applicable for argument types: () values: {}

Parent.java

package test
public class Parent{
	private String parentMethodB(){
		return "parentMethodB";
	}
	protected String parentMethodC(){
		def closure={
				return parentMethodB()}
		return closure()
	}
}

Child.java

package test
public class Child extends Parent{
	public static void main(def args){
		Child c = new Child();
		println(c.parentMethodC())
	}	
}

Issue Links

depends upon

GROOVY-2503 MOP 2.0 design inflluencing issues

GROOVY-3010 fix private field visibility

is duplicated by

GROOVY-2565 Exception with inheritance and private method calls from a closure

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Raoul Becke added a comment - 04/Oct/08 2:23 AM

Hi,
This issue can be "solved" (not really a solution) by turning the visility of method "private String parentMethodB()

{...}" to protected: "protected String parentMethodB(){...}

".
Regards
Raoul

Show

Raoul Becke added a comment - 04/Oct/08 2:23 AM Hi, This issue can be "solved" (not really a solution) by turning the visility of method "private String parentMethodB() {...}" to protected: "protected String parentMethodB(){...} ". Regards Raoul

Hide

Permalink

blackdrag blackdrag added a comment - 05/Oct/08 9:22 AM

this is more or less a known case. It is the result of a limitation in the current MOP. Since we plan to change the MOP in 2.0 I am setting the fix target for this to 2.0

Show

blackdrag blackdrag added a comment - 05/Oct/08 9:22 AM this is more or less a known case. It is the result of a limitation in the current MOP. Since we plan to change the MOP in 2.0 I am setting the fix target for this to 2.0

blackdrag blackdrag made changes - 05/Oct/08 9:22 AM