On Aug 8, 2012, at 7:35 PM, Camillo Bruni wrote: > nope they won't work either... > I changed all of that in 2.0's FS overhaul. Maybe we should port these > changes back to 1.4 to support a working version of FS there. > > All the stream selectors in 1.4 create a FSFileStream or so, which is a > incomplete reimplementation of FileStream. They might work for a very limited > set of operations, but AFAIK there is a big mem leak of low level file > handlers which eventually will crash the VM. > > Porting the changes back to 1.4 for the FileStream subpart should be a 0.5h > task (for me ;)). > > If esteban agrees to include these changes in 1.4 I am willing to create a > patch :)
thanks camillo I think that this is a good move. > > > On 2012-08-08, at 19:32, Dale Henrichs <[email protected]> wrote: > >> Cami, >> >> How about writeStream* and readStream* are those working? It looks like you >> used those variants in your FileTree pull request... >> >> Thanks, >> >> Dale >> >> ----- Original Message ----- >> | From: "Camillo Bruni" <[email protected]> >> | To: [email protected] >> | Sent: Wednesday, August 8, 2012 10:06:18 AM >> | Subject: Re: [Pharo-project] FileSystem differences between Pharo-2.0 and >> Pharo-1.4 >> | >> | in pharo 1.4 #fileStream and #fileStreamDo: & Co are not working >> | properly... >> | You'll still have to use something like >> | FileStream fileNamed: reference fullName >> | otherwise it should more or less work. >> | >> | >> | On 2012-08-08, at 18:36, Dale Henrichs <[email protected]> wrote: >> | >> | > I'm starting a port of FileTree to Pharo-2.0 and I'm planning on >> | > using Pharo-1.4 (summer) to do the actual port, since I can't run >> | > my development environment in Pharo-2.0 (chicken and egg problem). >> | > >> | > I'm wondering if there are any significant differences between the >> | > FileSystem implementations on the two platforms that I should be >> | > aware of... >> | > >> | > Dale >> | > >> | >> | >> | >> > >
