[Moose-dev] Re: FM(Null)(Multi)MultivalueLink has confusing printOn:

Hi, Moose does not redefine printOn: :). If some printOn: does not make sense, it's a bug and should be fixed. For display purposes, we use mooseDisplayStringOn: and gtDisplayOn:. We should start to kill mooseDisplayStringOn:. Doru On Thu, Sep 24, 2015 at 10:09 AM, Nicolas Anquetil &lt;nicolas.anquetil(a)inria.fr <mailto:nicolas.anquetil@inria.fr>> wrote: I always had an issue with the inspector and printOn: in Moose My use of the inspectr is in link with the debugger to understand the details of some behaviour. When I do debugging, I want to know precisely and accuratly what I am looking at. But because Moose redefines printOn: to be somehow user friendly, it often gets in the way by printing things that are not the real nature of the object. This case is one example of my problem I think the real solution should be to have two printing methods, one tor internal use (debugger, inspector) and another for users. The two are very different and they have different needs nicolas On 23/09/2015 13:58, Peter Uhnák wrote: _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- www.tudorgirba.com <http://www.tudorgirba.com> "Every thing has its own flow" _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev