Re: toDebugString as a Groovy core concept

2018-01-03 Thread mg
PS: I sent my reply from my son's gmail dev account, sorry for any  potentialy confusion :-) Ursprüngliche Nachricht Von: Guillaume Laforge Datum: 03.01.18 22:41 (GMT+01:00) An: d...@groovy.apache.org Cc: users@groovy.apache.org Betreff: Re: toDebugString as a Groovy

Re: toDebugString as a Groovy core concept

2018-01-03 Thread Ahm Avoby
Hi Guillaume, thanks for that question. I always felt GDK Object#dump() was meant to be used "as is", not to be overridden (overriding not mentioned in the Object doc, although there is of course nothing prohibiting one technically to do so). I also think that the name (while concise) is easy to

Re: toDebugString as a Groovy core concept

2018-01-03 Thread Guillaume Laforge
Out of curiosity, you know about the dump() method on Object? How close / different is it from your proposal of toDebugString()? (dump() had that same purpose initially) Guillaume On Wed, Jan 3, 2018 at 6:39 PM, MG wrote: > Hi all, > > I have created a jira for my proposed toDebugString Groovy

toDebugString as a Groovy core concept

2018-01-03 Thread MG
Hi all, I have created a jira for my proposed toDebugString Groovy feature: https://issues.apache.org/jira/browse/GROOVY-8431 Cheers, mg