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
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:
Hi,
Indeed, DeepTraverser is the project to look at. I started it from the code of
Mariano, and then Stefan Rechhart reimplemented it from scratch to make it very
fast (e.g. traversing subclasses of a class is only 10% slower than the hard
coded withAllSubclassesDo:) and to make it work like a
Hello.
I try to look how many classes has "isVariable=true" and "instSize>0". And
I found two strange cases: PathTests and FileReferenceTest is variable
classes. Why they are variable?
And more general: how classes become variable? For example Path isVariable
= true. But I not see initialize
Thank's Sven.
I not noticed it.
2015-12-24 10:49 GMT+01:00 Sven Van Caekenberghe :
> Denis,
>
> > On 24 Dec 2015, at 10:31, Denis Kudriashov wrote:
> >
> > Hello.
> >
> > I try to look how many classes has "isVariable=true" and "instSize>0".
> And I found
Denis,
> On 24 Dec 2015, at 10:31, Denis Kudriashov wrote:
>
> Hello.
>
> I try to look how many classes has "isVariable=true" and "instSize>0". And I
> found two strange cases: PathTests and FileReferenceTest is variable classes.
> Why they are variable?
Those are
Hi Denis,
This is a bit old, but it might help you understand a few things more:
https://marianopeck.wordpress.com/2011/05/07/class-formats-and-compiledmethod-uniqueness/
(forget a bit about the CompiledMethod explanation)
Cheers,
On Thu, Dec 24, 2015 at 6:57 AM, Denis Kudriashov
Okay!
Thanks!
Alexandre
> On Dec 23, 2015, at 7:26 PM, Peter Uhnák wrote:
>
> The problem with instance-side examples is that you need an instance
> to work with (otherwise there is not much point of having it on the
> instance-side), unless there would be pragma for it...
>