On Tue, Jun 5, 2012 at 3:36 PM, Mariano Martinez Peck <[email protected] > wrote:
> Guys..the fact of having to make everything deprecated instead of removing > it is really a pain. Now ReferenceStream is not removed but > deprecated..meaning that it *should* work. So instead of removing > everything I have to change it a lot so that it "still" works but > deprecated. Can we just assume that ReferenceStream will be removed in 2.0 > please? In addition, if someone is really worried about ReferenceStream then he can always do a fileout of 1.4 and import it in Pharo 2.0 (and adapt it if necessary) > > > On Tue, Jun 5, 2012 at 1:32 PM, Mariano Martinez Peck < > [email protected]> wrote: > >> Ok. Perfect. So let's assume DataStream is used only for Motnicello. I >> will rename it to MCDataStream, move it to Monticello Package and see all >> what I can remove/clean. >> I will let you know. >> >> Cheers >> >> >> On Tue, Jun 5, 2012 at 12:51 PM, Esteban Lorenzano >> <[email protected]>wrote: >> >>> +1 >>> >>> On Jun 4, 2012, at 6:15 PM, Damien Cassou wrote: >>> >>> > On Mon, Jun 4, 2012 at 6:09 PM, Pavel Krivanek < >>> [email protected]> wrote: >>> >> I think it is a good proposal. Then it can be in separate package or >>> as part >>> >> of MC package. >>> > >>> > I would put DataStream and its friends within the monticello package, >>> > and prepend MC to their names. Then, you can clean the resulting >>> > classes if you want to. >>> > >>> > -- >>> > Damien Cassou >>> > http://damiencassou.seasidehosting.st >>> > >>> > "Lambdas are relegated to relative obscurity until Java makes them >>> > popular by not having them." James Iry >>> > >>> >>> >>> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > > -- Mariano http://marianopeck.wordpress.com
