> You are right, this would foul up the nextPut primitive for WriteStream, so
you would 
> have to add the new field separately after those defined in ReadStream and
WriteStream
>  rather than doing it in one place in PositionableStream.
Duh, talk about missing the obvious one! Still, the prim recovery code
handles it just fine....

>  Otherwise, it should be str
> aightforward, but a bit of a shame to add something that's hardly ever
> used (though, I admit, frustrating when it's not there).
Well, a similar argument could be made about a lot of stuff in Smalltalk;
how often does anyone actually use metaprogramming, reified Contexts, etc
etc? Yet it would be a much lesser system if they were not there. I find
considerable value in (for want ofa better term) correctness, not to
mention pragmatic value in minimizing nasty surprises.

tim


-- 
Strange OpCodes: BOMB: Burn Out Memory Banks
Tim Rowledge:  rowledge at interval.com (w)  +1 (650) 842-6110 (w)
 tim at sumeru.stanford.edu (h)  <http://sumeru.stanford.edu/tim>