Re: [Pharo-dev] Executive Summary of the recent FileStream Changes

so I chose to implement the more general YAML algorithm instead. > Sent: Friday, March 16, 2018 at 6:44 AM > From: "Sven Van Caekenberghe" <s...@stfx.eu> > To: "Pharo Development List" <pharo-dev@lists.pharo.org> > Subject: Re: [Pharo-dev] Executive Summary of th

Re: [Pharo-dev] Executive Summary of the recent FileStream Changes

Sean you can really help on this one. Stef On Fri, Mar 16, 2018 at 5:47 PM, Sean P. DeNigris wrote: > Stephane Ducasse-3 wrote >> we are planning to migrate a selection of the old >> deprecated methods (of Pharo 30, 40, 50, 60) into a MigrationPackage >> with

Re: [Pharo-dev] Executive Summary of the recent FileStream Changes

Stephane Ducasse-3 wrote > we are planning to migrate a selection of the old > deprecated methods (of Pharo 30, 40, 50, 60) into a MigrationPackage > with deprecatedWithTransform rule > to help the migration of the old code to new one. Cool!!! - Cheers, Sean -- Sent from:

Re: [Pharo-dev] Executive Summary of the recent FileStream Changes

Hi Monty We will keep the old stuff around in a kind of deprecated packages. Now in the long term we do not intend to maintain them forever because we will collapse under the load. You see it was either that clean up or modules so at the end ***Pharo*** should move on because this is our

Re: [Pharo-dev] Executive Summary of the recent FileStream Changes

+ 1 Ah what a relief. Thanks a lot guille for all this good energy. BTW I also like the pattern. We should apply the same to OPAL. Do not mix API and add a wrapper for the backward compatible so that the new API is untouched. I really like that way. Now we should replace cr by newline :)

Re: [Pharo-dev] Executive Summary of the recent FileStream Changes

> On 16 Mar 2018, at 07:05, monty wrote: > >> Sent: Thursday, March 15, 2018 at 4:01 PM >> From: "Sven Van Caekenberghe" >> To: "Pharo Development List" >> Subject: [Pharo-dev] Executive Summary of the recent FileStream Changes

Re: [Pharo-dev] Executive Summary of the recent FileStream Changes

> On 15 Mar 2018, at 23:36, Nicolas Cellier > wrote: > > Very good initiative! > It's worth a few hick-ups. Thanks, the really hard work is in the all the using code, writing against simpler APIs. It will be a while before all the dust settles and all

Re: [Pharo-dev] Executive Summary of the recent FileStream Changes

> Sent: Thursday, March 15, 2018 at 4:01 PM > From: "Sven Van Caekenberghe" > To: "Pharo Development List" > Subject: [Pharo-dev] Executive Summary of the recent FileStream Changes > > Executive Summary of the recent FileStream Changes > > In Pharo 7

Re: [Pharo-dev] Executive Summary of the recent FileStream Changes

Very good initiative! It's worth a few hick-ups. I've tried to reduce RWBinaryOrTextStream usage in Squeak maybe 10 years ago, but you know it very well, the last places which are resisting are the more intricated and convoluted. I call it the SwiisKnifeStream and allways wandered why we would