5:43 AM
> From: stepharo <steph...@free.fr>
> To: pharo-dev@lists.pharo.org
> Subject: Re: [Pharo-dev] lineConversion for WriteStream
>
>
> > So it looks to me like LF wins!
> > It may take a while and some effort, but can we agree on a three point
> > st
: "Peter Uhnák" <i.uh...@gmail.com>
To: "Pharo Development List" <pharo-dev@lists.pharo.org>
Subject: Re: [Pharo-dev] lineConversion for WriteStream
Well I was saving e.g. STON or XML file… but some apps outside didn't
particularly like it… even `cat` doesn't like CR.
Any
> On 27 May 2016, at 05:07, Ben Coman wrote:
>
> On Fri, May 27, 2016 at 2:30 AM, Sven Van Caekenberghe wrote:
>>
>>> On 26 May 2016, at 20:20, Peter Uhnák wrote:
>>>
>>> Well I was saving e.g. STON or XML file… but some apps outside
On Fri, May 27, 2016 at 2:30 AM, Sven Van Caekenberghe wrote:
>
>> On 26 May 2016, at 20:20, Peter Uhnák wrote:
>>
>> Well I was saving e.g. STON or XML file… but some apps outside didn't
>> particularly like it… even `cat` doesn't like CR.
>
> Well, STONWriter,
Ah, thanks, I'll take a look at that.
I was using STON toStringPretty:
On Thu, May 26, 2016 at 8:30 PM, Sven Van Caekenberghe wrote:
>
> > On 26 May 2016, at 20:20, Peter Uhnák wrote:
> >
> > Well I was saving e.g. STON or XML file… but some apps outside
> On 26 May 2016, at 20:20, Peter Uhnák wrote:
>
> Well I was saving e.g. STON or XML file… but some apps outside didn't
> particularly like it… even `cat` doesn't like CR.
Well, STONWriter, NeoJSONWriter and NeoCSVWriter allow you to set the line end
convention, you are
Well I was saving e.g. STON or XML file… but some apps outside didn't
particularly like it… even `cat` doesn't like CR.
Anyway; this is not system-breaking problem, just annoying.
Peter
On Thu, May 26, 2016 at 2:50 PM, Sven Van Caekenberghe wrote:
>
> > On 26 May 2016, at 14:06,
> On 26 May 2016, at 14:06, Peter Uhnák wrote:
>
>
>
> On Thu, May 26, 2016 at 1:40 PM, Sven Van Caekenberghe wrote:
>
> > On 26 May 2016, at 13:29, Peter Uhnák wrote:
> >
> > > In general I would say that you should write either
On Thu, May 26, 2016 at 1:40 PM, Sven Van Caekenberghe wrote:
>
> > On 26 May 2016, at 13:29, Peter Uhnák wrote:
> >
> > > In general I would say that you should write either something
> platform specific or you write something specific
> >
> > Except that I
> On 26 May 2016, at 13:29, Peter Uhnák wrote:
>
> > In general I would say that you should write either something platform
> > specific or you write something specific
>
> Except that I cannot do that because the system doesn't support neither.
> And the fact that the
> In general I would say that you should write either something platform
specific or you write something specific
Except that I cannot do that because the system doesn't support neither.
And the fact that the default line ending is CR is just bullshit… it's
2016, not 1986.
On Thu, May 26, 2016
MultiByteFileStream is terrible (too complex) because it does too much (at
once). Let's keep WriteStream simple (and even simplify it). You do not want
characters that change magically.
That being said, line end conventions can be a pain. In general I would say
that you should write either
Is there a reason why only MultiByteFileStream provides lineEndConvention:
and not WriteStream?
The problem is that if I use MemoryStore in tests it breaks, because
DiskStore and MemoryStore return different write streams.
'/tmp/test.txt' asFileReference writeStream ==> "MultiByteFileStream:
13 matches
Mail list logo