🚀 go-pugleaf

ArrayedCollection's printOn method uses storeOn to print its contents.  This,
in my humble opinion, makes no sense whatsoever.  If the user wanted storage-
level detail, the user would have used storeOn.  Consider:  an array consisting
of two arrays, each of which holds three integers.  If you invoke this array's
printOn method (*not* storeOn), which would you rather see?

a) current situation:  ArrayedCollection's printOn uses storeOn

     Array (((Array basicNew: 3) at: 1 put: 1; at: 2 put: 2; at: 3 put: 3;
     yourself)((Array basicNew: 3) at: 1 put: 4; at: 2 put: 5; at: 3 put: 6;
     yourself))


b) better (?) situation:  ArrayedCollection's printOn uses printOn

     Array (Array (1 2 3) Array (4 5 6))

Is there a good reason why storeOn is used?  My Smalltalk version is 1.1.1, if
that is an important consideration.  (Is this the most current version?)

                            Ben Liblit
                            BRL102 @ psuvm.psu.edu -- BRL102 @ psuvm.bitnet
                            Liblit @ cs.psu.edu
                            "Fais que tes reves soient plus longs que la nuit."