On Sun, Dec 11, 2011 at 11:32 AM, Stéphane Ducasse < stephane.duca...@inria.fr> wrote:
> Indeed this is fun I was doing the same :) > Now I do not understand why some parts of the system uses dataStream, > others ReferenceStream and finally others SmartRefStream > why not all of them use SmartRefStream. > It is not that I like these guys, but their class comments are pretty clear: - DataStream does NOT handle cycles, but hence it may be faster in certain scenarios. I guess that for example, Monticello is sure that in its definitions, there cannot be cycles. In addition, it doesn't take into account variables names/order and hence class reshape isn't supported. - ReferenceStream supports cycles but still doesn't support class reshape. - SmartRefStream supports cycles and class reshape. > Stef > > On Dec 11, 2011, at 10:43 AM, Marcus Denker wrote: > > > Hi, > > > > We should minimize the use of SmartRefStream... so we can remove it > eventually. > > > > I already did a little bit (e.g. removing BitmapStreamTests). These are > the next steps: > > > > Issue 5081: Remve Morph saving to file/loading > > http://code.google.com/p/pharo/issues/detail?id=5081 > > > > Anyone needs this? > > > > Issue 5084: Remove textStyle FileOut > > http://code.google.com/p/pharo/issues/detail?id=5084 > > > > Is this used? Strange corner of the system... lots of dead code. > > > > Issue 5083: remove unused methods from SmartRefStream > > http://code.google.com/p/pharo/issues/detail?id=5083 > > > > Towards removing it alltogether. > > > > > > > > > > -- > > Marcus Denker -- http://marcusdenker.de > > > > > > > -- Mariano http://marianopeck.wordpress.com
