Nuking any piece of Squeak code with the word 'Stream' in it might be
a good idea anyway ;)
Seriously, I never dared, because it's one of the few senders of
#byteEncode: along with #encodePostscriptOn:...
But looking at the code, it seems to be a very generic visitor
pattern, and not really used directly by PostscriptEncoder, but by
parallel PrintEncoder and StoreEncoder...
It seems to just be a proof of concept for replacing printOn:/storeOn:
Such a proof of concept with no comment, no use case, and loosy
implementation might well go out of the image, I won't cry...

Nicolas

2013/2/24 Eliot Miranda <eliot.miranda at gmail.com>:
> Hi All,
>
>     is printOnStream: useful?  Anyone know what it was for?  It looks
> wrong to me.  It prints strings rather than objects.  e.g. thisContext
> method printOn: Transcript writes
>         'a CompiledMethod'
> to Transcript, rather than
>         a CompiledMethod
> Further some of the method stamps are 1901.
>
> The Pharo guys have nuked this.  Looks like it might be a good idea.
> --
> best,
> Eliot
>