[GROOVY-2732] GString doesn't call correct toString method when it's been changed via the metaClass mechanism

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 1.5.4
• Environment: linux
• Flags: Patch
• Assignee: Unassigned
• Reporter: brandon niemczyk
• Created: 08/Apr/08 15:55
• Updated: 05/Apr/15 14:44
• Resolved: 08/Apr/08 16:57

Description

This is best shown by a small example. I've attached a trivial patch as well.

class A {
String toString()

{ "unchanged"; }

}

A.metaClass.toString = { ->
"changed";
}

def a = new A();
println a.toString();
println "${a}";

brandon@Brandon:~/localtmp/groovy-1.5.4$ unset GROOVY_HOME
brandon@Brandon:~/localtmp/groovy-1.5.4$ groovy-unpatched test.groovy
changed
unchanged
brandon@Brandon:~/localtmp/groovy-1.5.4$ groovy test.groovy
changed
changed

Issue Links

• duplicates: GROOVY-2599 unable to overwrite toString() via MOP in some cases