2011/12/11 Stéphane Ducasse <stephane.ducasse@inria.fr>:
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.
Stef
That's a very good question. Where should design decisions be documented? On one side, we should have requirements that we document with some high level TestCase. But whether the implementation is guided by time/memory efficiency, code simplicity, or just historically available packages is not easily described by tests. Obviously, you would have a hard time discovering this in legacy code (digging squeak wiki and mailing list?). The question should apply to Pharo too. Pharo is young, so maybe all design decisions can be retrieved by virtue of human memory... But will it be the case in 5 years? Nicolas
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