[Pharo-dev] Debugger recursion
Mariano Martinez Peck
marianopeck at gmail.com
Tue Aug 27 16:21:38 EDT 2013
If you take a look to Ghost proxies, in the proxy handler I have a
dictionary in which users can define exceptions. That means, that the proxy
handler will do something different than the expected action (like
forwarding the message to another object). By default, I added some helper
methods that add some of these exceptions. One of these, where a list of
method to proper debug/inspect proxies. And the nice thing of being a
dictionary is that you can enable/disable them even on the fly.
On Tue, Aug 27, 2013 at 5:09 PM, Igor Stasenko <siguctua at gmail.com> wrote:
> On 24 August 2013 14:18, jan.struz <public+pharo at struz.cz> wrote:
>> Stéphane Ducasse wrote
>> > On Aug 23, 2013, at 7:13 PM, jan.struz <
>> > public+pharo@
>> > > wrote:
>> >> Proxy implementation
>> > did you have a look at Ghost because mariano spent nearly a year on it.
>> > I do not really know what are the messages supposed to be supported by
>> > ProtoObject to be debugged
>> > May be it is not in the contract of ProtoObject and as such it produces
>> > normally an infinite loop.
>> > Stef
>> ok, so the rule is: never subclass ProtoObject to make Debugger crazy..
>> I will definitely look at Ghost, it has already been on my todo list..
>> i would say:
> - if you subclass from ProtoObject then you are on your own.. don't expect
> any standard tools to work anymore (including debugger, of course).
> And no, there is no 'fix' for that.. except from merging ProtoObject with
> which kills the purpose of having ProtoObject class.
>> Save The World!
>> View this message in context:
>> Sent from the Pharo Smalltalk Developers mailing list archive at
> Best regards,
> Igor Stasenko.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pharo-dev