Hello guys,
i'd like to discuss with you an idea of having a specific methods in
Object class for a better and more clever behavior when debugging.
For those of you who are using different kinds of proxies, the main
problem with them that you should override the #printOn:
or #printString methods i
good idea!
We will add that in pharo if you open a bug item ticket.
Stef
On Sep 7, 2009, at 5:02 PM, Igor Stasenko wrote:
> Hello guys,
> i'd like to discuss with you an idea of having a specific methods in
> Object class for a better and more clever behavior when debugging.
>
> For those of you
2009/9/7 Stéphane Ducasse :
> good idea!
> We will add that in pharo if you open a bug item ticket.
> Stef
>
I could add it easily. But first we should make a good expertise, if
this change is worth doing.
Because for Object it means a trivial addition of a method, but for
Debugger/Inspector and o
On 7 sep 2009, at 17.02, Igor Stasenko wrote:
> Hello guys,
> i'd like to discuss with you an idea of having a specific methods in
> Object class for a better and more clever behavior when debugging.
>
> For those of you who are using different kinds of proxies, the main
> problem with them that
Well, if the goal is to be able to differentiate between two objects who
should behave similar in all cases except when you print them while
debugging, I can't really think of any better ways :)
Playing the devil's advocate, here's two things to consider:
- Some people will likely expect *all* pro
2009/9/7 Peter Hugosson-Miller :
> On 7 sep 2009, at 17.02, Igor Stasenko wrote:
>
>> Hello guys,
>> i'd like to discuss with you an idea of having a specific methods in
>> Object class for a better and more clever behavior when debugging.
>>
>> For those of you who are using different kinds of pr
2009/9/7 Henrik Johansen :
> Well, if the goal is to be able to differentiate between two objects who
> should behave similar in all cases except when you print them while
> debugging, I can't really think of any better ways :)
>
> Playing the devil's advocate, here's two things to consider:
> - So
I think it is a reasonable approach. GemStone has a few debugger
switches which affect the debugging of proxies ( at least stubs) so I
mention that since it is a similar area. Where your extension perhaps
wouldn't scale is if this became an enthusiastic growth of API if you
found other useful thing
