[GROOVY-2599] unable to overwrite toString() via MOP in some cases

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.5.4
• Component/s: groovy-runtime
• Assignee: Unassigned
• Reporter: Lee Butts
• Created: 13/Feb/08 01:59
• Updated: 02/Jan/22 23:50

Description

If toString is overridden via the metaClass then "${obj}" != obj.toString().

Test case below

class DateTest extends GroovyTestCase {

    void testToString(){

        Date.metaClass.toString = { ->
            'boogie'
        }
       
        def date = new Date()
        assertEquals('boogie', date.toString())
        assertEquals( date.toString(), "${date}") //fails
    }
}

Paul King gave this pointer as to where the problem is:

"Yes, the final line of InvokerHelper.format() should be something like:

return (String) invokeMethod(arguments, "toString", EMPTY_ARGS);
//return arguments.toString();

to make your example work."

Issue Links

• is duplicated by: GROOVY-2732 GString doesn't call correct toString method when it's been changed via the metaClass mechanism
• is related to: GROOVY-10073 Unable to use custom string representation in GString template
• relates to: GROOVY-2801 Override toString in coerced Map fails for interfaces but is ok for concrete classes