Hi: On 30 Nov 2010, at 13:56, Schwab,Wilhelm K wrote:
A possible wrinkle: what about using Linux to write a file for a Windows user? That is why I proposed to use MultiByteFileStream LineEndDefault.
There are methods in MultiByteFileStream to set it explicitly. So, it could be either set in a save dialog, or a user preference somewhere, I guess. Best regards Stefan PS: The file stream should be initialized on creation with MultiByteFileStream LineEndDefault, otherwise it is not thread/RoarVM-safe...
________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Stefan Marr [pharo@stefan-marr.de] Sent: Tuesday, November 30, 2010 7:13 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Changesets with LF/CRLF instead of CR?
Hello:
On 30 Nov 2010, at 09:20, Stéphane Ducasse wrote:
as a general principle, I'm open to change for the better :) Now how much? - cost to do Cleaning it up completely does not looks like a simple/localized change to a single method.
There are 'aFileStream cr' message sends all over the place, which from my perspective are wrong in the sense that they are not platform independent. I guess the best way would be to have something like 'aFileStream nl' or 'lineEnd' instead. Where nl/lineEnd uses MultiByteFileStream LineEndDefault.
Best regards Stefan
-- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525
-- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525