Smalltalk › Instantiations

[8.5.2] Inspector defect for Bag

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

2 messages Options

Richard Sargent

[8.5.2] Inspector defect for Bag

Administrator

If one inspects the result of evaluating the following expression:

Bag
    with: Object new
    with: Object new
    with: Object new
    with: Object new

the inspector window lies.

When the window first opens, "self" is expanded to show the "occurrenceDictionary". Their respective "values" show: Bag(an Object an Object an Object an Object ) and LookupTable(1 1 1 1 ), as one would expect.

However, if you expand the occurrence dictionary, things go awry. It only shows the existence of a single "an Object"!

I suspect this error affects a number of versions, not solely 8.5.2.

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/va-smalltalk.
For more options, visit https://groups.google.com/groups/opt_out.

Seth Berman

Re: [8.5.2] Inspector defect for Bag

Hi Richard,

Nice find. I have opened case 53483.

In short, changing 'self keys collect:' to 'self keys asArray collect:' in KeyedCollection>>inspectorVariables

is one possible fix.

This is scheduled to be fixed in 8.6.1

-- Seth Berman

On Friday, January 24, 2014 4:10:09 PM UTC-5, Richard Sargent wrote:

If one inspects the result of evaluating the following expression:

Bag
    with: Object new
    with: Object new
    with: Object new
    with: Object new

the inspector window lies.

When the window first opens, "self" is expanded to show the "occurrenceDictionary". Their respective "values" show: Bag(an Object an Object an Object an Object ) and LookupTable(1 1 1 1 ), as one would expect.

However, if you expand the occurrence dictionary, things go awry. It only shows the existence of a single "an Object"!

I suspect this error affects a number of versions, not solely 8.5.2.