Whether used or not, anything under ReadWriteTextStream hierarchy should be refactored then deprecated. The name already tells : I could be a read stream a write stream, a text stream, what else ? I suggest to first rename it ReadWriteTextStreamWhatElse. Then to provide a good comment: This class was detected, selected, infected, neglected, deprecated then rejected.
;) cheers 2011/2/9 Guillermo Polito <[email protected]>: > Okok > http://code.google.com/p/pharo/issues/detail?id=3686 > Open issue to *deprecate* it :P. > > On Tue, Feb 8, 2011 at 8:06 PM, <[email protected]> wrote: >> >> "If you can't comment and can't find references to it in {core,dev}? >> image, then remove it!" >> >> >> >> Em 08/02/2011 19:11, laurent laffont < [email protected] > >> escreveu: >> Time to add >> >> COTDC rule #2: If you can't comment it, remove it. >> >> Indeed it's compatible with the goal: each day, one less not commented >> class ! >> >> Laurent >> >> >> >> On Tue, Feb 8, 2011 at 10:01 PM, Stéphane Ducasse >> <[email protected]> wrote: >> >> PseudoFileStream ... >> may be we could remove it :) >> >> Stef >> >> >> >> >> On Feb 8, 2011, at 5:39 PM, laurent laffont wrote: >> >> > Today: PseudoFileStream >> > >> > Comment Of The Day Contest - One Day One Comment >> > Rules: Each day a not commented class is elected. Each day the best >> comment will be integrated with name of the author(s). >> > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest >> > >> > Laurent >> > >> >> >> >> >> >> >> >> >> >> >> > >
