> That still leaves me with the nagging question: are there good reasons 
> for Text to inherit from SequenceableCollection given that it 
> overrides most collection behavior. I can see that that was so when 
> the IV runs did not exist yet. The reason for me raising this point in 
> the first place was that the TextStream nextPutAll: bug in the header 
> of this thread was caused as well by Text not being a collection. 
> Well, I guess that is up to KCP.

We will not work on that because we have enough to do with the kernel.
Why don't you propose some code to be evaluated?

Stef

> Cheers.
>
>
> At 06:46 AM 9/29/03, you wrote:
>> On Mon, 29 Sep 2003 06:12:32 -0700 Frits Swinkels 
>> <frits.swinkels at shaw.ca> wrote:
>> >That is not what happens in my 3.5: It shows "a Text for bla, bla" 
>> alright,
>> >but a toggle gives me a long list of the individual letters of the 
>> text as
>> >if Text was nothing but a collection. I do not see the runs while an
>> >inspector does show them. If the runs show up on your image, we have 
>> a
>> >bizarre problem.
>>
>> Ah, my image is 3.2. You can simply remove 
>> SequenceableCollection>>explorerContents to get the behavior I 
>> describe.
>>
>> Cheers,
>> Bob
>
>