Re: [Pharo-dev] Are Critical Tools Becoming Too Brittle?

Sven Van Caekenberghe-2 wrote > Are you sure your #printString is OK ? Aha! @$!$%!#$!#$#@ I got bitten for the umpteenth time by the #name trap. My custom #printOn: was calling #name, which I hadn't yet defined, and so called the default implementation, which sends #printString => infinite

Re: [Pharo-dev] Are Critical Tools Becoming Too Brittle?

Max Leske wrote > Did you send #basicInspect? That should still give you the original > minimal inspector. Good tip! I didn't think of that. I see it's even in the context menu :) - Cheers, Sean -- View this message in context:

Re: [Pharo-dev] Are Critical Tools Becoming Too Brittle?

We should integrate the Mirror package of guillermo. But he was busy and sick. Stef Le 16/12/15 23:03, Esteban A. Maringolo a écrit : Yeap, they are in the VM, I used them with the fileout you sent me. I guess Tudor was referring to the spur *image* and not the VM. The issue is already

Re: [Pharo-dev] Are Critical Tools Becoming Too Brittle?

Would certainly be interesting. Until mirrors come, I would still use the primitives as there are only a few places and we can adapt later on again. Cheers, Doru > On Dec 17, 2015, at 8:06 PM, stepharo wrote: > > We should integrate the Mirror package of guillermo. But he

Re: [Pharo-dev] Are Critical Tools Becoming Too Brittle?

I am waiting for the Spur image because it should already have the primitives and I will get back to the ProtoObject issue. Could you open an issue in the meantime? Cheers, Doru > On Dec 16, 2015, at 6:31 PM, Esteban A. Maringolo > wrote: > > Doru, > > Did you fix

Re: [Pharo-dev] Are Critical Tools Becoming Too Brittle?

Doru, Did you fix the issue involving instances of subclasses of ProtoObject? Esteban A. Maringolo 2015-12-16 2:46 GMT-03:00 Tudor Girba : > Hi, > > Indeed, please help us isolate that case. > > Cheers, > Doru > > >> On Dec 15, 2015, at 11:49 PM, Sven Van Caekenberghe

Re: [Pharo-dev] Are Critical Tools Becoming Too Brittle?

On Wed, Dec 16, 2015 at 2:02 PM, Tudor Girba wrote: > Yes, but they were not in the image and as the Spur image was coming > anyway I thought I just wait for it :) > +1 then :) > > Doru > > > > On Dec 16, 2015, at 10:55 PM, Eliot Miranda >

Re: [Pharo-dev] Are Critical Tools Becoming Too Brittle?

Yes, but they were not in the image and as the Spur image was coming anyway I thought I just wait for it :) Doru > On Dec 16, 2015, at 10:55 PM, Eliot Miranda wrote: > > > > On Wed, Dec 16, 2015 at 12:03 PM, Tudor Girba wrote: > I am waiting

Re: [Pharo-dev] Are Critical Tools Becoming Too Brittle?

On Wed, Dec 16, 2015 at 12:03 PM, Tudor Girba wrote: > I am waiting for the Spur image because it should already have the > primitives and I will get back to the ProtoObject issue. Could you open an > issue in the meantime? > The mirror primitives should be in the old VM

Re: [Pharo-dev] Are Critical Tools Becoming Too Brittle?

Yeap, they are in the VM, I used them with the fileout you sent me. I guess Tudor was referring to the spur *image* and not the VM. The issue is already opened: https://pharo.fogbugz.com/f/cases/17170/Context-missing-primitives Esteban A. Maringolo 2015-12-16 18:55 GMT-03:00 Eliot Miranda

[Pharo-dev] Are Critical Tools Becoming Too Brittle?

I just tried to inspect a domain object and I froze my image and had to force quit. How do I debug this? And, more importantly, when an error is encountered in a critical, basic tool like this, should there be some reasonable bare-bones alternative, like the emergency debugger? Not being able to

Re: [Pharo-dev] Are Critical Tools Becoming Too Brittle?

I assume you are using the GT inspector. Do you have custom gt inspector presentations ? Are you sure your #printString is OK ? There is also a 'Basic Inspect It' menu item ... Can you isolate it so that we can see it, try it ? > On 15 Dec 2015, at 23:21, Sean P. DeNigris

Re: [Pharo-dev] Are Critical Tools Becoming Too Brittle?

Hi, Indeed, please help us isolate that case. Cheers, Doru > On Dec 15, 2015, at 11:49 PM, Sven Van Caekenberghe wrote: > > I assume you are using the GT inspector. Do you have custom gt inspector > presentations ? Are you sure your #printString is OK ? > > There is also a

Re: [Pharo-dev] Are Critical Tools Becoming Too Brittle?

> On 15 Dec 2015, at 23:21, Sean P. DeNigris wrote: > > I just tried to inspect a domain object and I froze my image and had to force > quit. How do I debug this? And, more importantly, when an error is > encountered in a critical, basic tool like this, should there be