They still use (binary) StandardFileStreams on Pharo and Squeak. But since it's done through dynamically chosen file stream factory classes (XMLFileReadStreamFactory and XMLFileWriteStreamFactory), it's easy add support for other stream classes. (The GemStone compat .mcz adds factories for GsFile read/write factories, for example).
#preferredImplementation selects which implementation to use in the hierarchy when there's more than one supported (#isSupportedImplementation). ___ montyos.wordpress.com > Sent: Monday, June 18, 2018 at 1:34 AM > From: "Sven Van Caekenberghe" <[email protected]> > To: "Any question about pharo is welcome" <[email protected]> > Subject: Re: [Pharo-users] Lost in stream > > > > > On 18 Jun 2018, at 02:18, monty <[email protected]> wrote: > > > > Also consider using XMLParser's built-in file reading support: > > #parseFileNamed:/#onFileNamed:. They work cross platform (Squeak, GS), and > > handle character decoding. > > Monty, do these (already) work with all the latest changes in Pharo 7, I mean > the deprecation of FileStream and subclasses as well as > [RW|MultiByte]BinaryOrTextStream for FileReference, File and Zn streams ? > > If not, we should help you. > > Sven >
