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-refe... ) The problem is that arrays printOn: does not check for already visited objects (squeak does this, but the implementation in pharo changed). For example, in Pharo 50 | myDict | myDict := Dictionary new. myDict at: #hello put: 'hello'. myDict at: #recurHello put: myDict. myDict inspect you can open the inspector, but selecting the first element in the "keys" tab makes the image unresponsive. The same happens if you select the #array instvar in the "raw" tab. 2015-08-29 15:16 GMT+02:00 H. Hirzel <hannes.hirzel@gmail.com>:
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 <marcus.denker@inria.fr> wrote:
On 29 Aug 2015, at 12:58, Andrei Chis <chisvasileandrei@gmail.com>
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-display-string-for-collection-ma...