No this doesn't even fully work for the GTInspector (even not in Pharo 5.0).
It is the same issue Ben discovered when working with the pointer explorer.
(http://forum.world.st/Proposal-for-LiteralArray-class-tp4803015.html
and
http://forum.world.st/Fwd-14827-ProtoObject-pointersTo-failing-circular
As for me no need to hurry. I switch now to Pharo 5 build 50287 in the
meantime. I will continue using that if I do not run into larger
problems.
--Hannes
On 8/29/15, Marcus Denker wrote:
>
>> On 29 Aug 2015, at 12:58, Andrei Chis wrote:
>>
>> Was there an issue/fix for this in Pharo 5?
>> It
> On 29 Aug 2015, at 12:58, Andrei Chis wrote:
>
> Was there an issue/fix for this in Pharo 5?
> It might be worth backporting to Pharo 4.
>
Maybe one related to what is printed for the dictionary.
It used to be very slow for large collections
https://pharo.fogbugz.com/f/cases/15311/The-displa
> On 29 Aug 2015, at 13:27, H. Hirzel wrote:
>
> On 8/29/15, Marcus Denker wrote:
>> It seems to be fixed in Pharo5 already. Debugger comes up within less than a
>> second and is usable.
>
> Very welcome.
> I assume you mean 'Inspector' (not debugger)
>
Yes.
Marcus
On 8/29/15, Andrei Chis wrote:
> Was there an issue/fix for this in Pharo 5?
> It might be worth backporting to Pharo 4.
If it is not a big effort, yes please.
>
> On Sat, Aug 29, 2015 at 12:06 PM, Marcus Denker
> wrote:
>
>> It seems to be fixed in Pharo5 already. Debugger comes up within les
On 8/29/15, Marcus Denker wrote:
> It seems to be fixed in Pharo5 already. Debugger comes up within less than a
> second and is usable.
Very welcome.
I assume you mean 'Inspector' (not debugger)
>
> Marcus
>> On 29 Aug 2015, at 11:57, H. Hirzel wrote:
>>
>> Andrei,
>>
>> Thanks for confir
Was there an issue/fix for this in Pharo 5?
It might be worth backporting to Pharo 4.
On Sat, Aug 29, 2015 at 12:06 PM, Marcus Denker
wrote:
> It seems to be fixed in Pharo5 already. Debugger comes up within less than
> a second and is usable.
>
> Marcus
> > On 29 Aug 2015, at 11:57, H.
It seems to be fixed in Pharo5 already. Debugger comes up within less than a
second and is usable.
Marcus
> On 29 Aug 2015, at 11:57, H. Hirzel wrote:
>
> Andrei,
>
> Thanks for confirming the bug.
>
> Report is here
>
>
> https://pharo.fogbugz.com/f/cases/16425/Pharo-4-0-Inspect
Andrei,
Thanks for confirming the bug.
Report is here
https://pharo.fogbugz.com/f/cases/16425/Pharo-4-0-Inspecting-a-recursive-data-structure-is-slow
--Hannes
On 8/29/15, Andrei Chis wrote:
> Hi Hannes,
>
> Can open a bug report?
> I though most recursive problems were fixed in the new i
Hi Hannes,
Can open a bug report?
I though most recursive problems were fixed in the new inspector.
Seems that there are still some related to printing recursive structures.
You can switch to the previous inspector (GTInspector
setGTInspectorEnabledStatus: false),
however, this bug seem to also k
Hello
I have realized that inspecting a recursive data structure is very
slow in Pharo 4.0
A test case:
| myDict |
myDict := Dictionary new.
myDict at: #hello put: 'hello'.
myDict at: #recurHello put: myDict.
myDict inspect
It takes a long time for the inspector to come up. And the image
freeze
11 matches
Mail list logo
