Yes that would be a good idea.
So I hope that we will be able to clean the stream part of Pharo.
But the problem is the users of streams. The stream API is too wide, people
expect hundreds of methods to be there, mixing characters and bytes, encodings,
line end conventions, infinite bufferi
using #asString there is wrong, IMHO, if the memory stream is on bytes it
should return a read stream reading bytes, if it is on characters, the read
stream should return characters.
> On 01 Mar 2016, at 21:13, Max Leske wrote:
>
>
>> On 01 Mar 2016, at 20:51, Udo Schneider wrote:
>>
>> On
> On 01 Mar 2016, at 20:51, Udo Schneider wrote:
>
> On 29/02/16 23:06, Sven Van Caekenberghe wrote:
>> I think it is not good to do this, better stick with bytes.
> Should I fix it and submit a slice or use a workaround in my code?
I don’t think it makes sense to change #readStream. I do think
On 29/02/16 23:06, Sven Van Caekenberghe wrote:
I think it is not good to do this, better stick with bytes.
Should I fix it and submit a slice or use a workaround in my code?
CU,
Udo
> On 01 Mar 2016, at 07:07, stepharo wrote:
>
> Hi sven
>
> I would like to get Xtreams (with a slightly modified API - no ++ and --) in
> Pharo 6.0.
Yes that would be a good idea.
> So I hope that we will be able to clean the stream part of Pharo.
But the problem is the users of streams. T
Hi sven
I would like to get Xtreams (with a slightly modified API - no ++ and
--) in Pharo 6.0.
So I hope that we will be able to clean the stream part of Pharo.
Stef
Le 29/2/16 23:06, Sven Van Caekenberghe a écrit :
On 29 Feb 2016, at 20:27, Udo Schneider wrote:
All,
is there any reason
We introduced #binaryReadStream and friends as a work around in Pharo 4. The
reason we didn’t fix the problem properly is that we’ve been waiting for the
introduction of XStreams in hopes of getting a cleaner stream API.
Max
> On 29 Feb 2016, at 23:06, Sven Van Caekenberghe wrote:
>
>
>> On
> On 29 Feb 2016, at 20:27, Udo Schneider wrote:
>
> All,
>
> is there any reason why MemoryFileSystemFile>>#readStream forces it's content
> to a String (#aString)?
>
> readStream
> ^ ReadStream on: self bytes asString from: 1 to: size
>
> I'm parsing XML files from an in-memory ZIP
All,
is there any reason why MemoryFileSystemFile>>#readStream forces it's
content to a String (#aString)?
readStream
^ ReadStream on: self bytes asString from: 1 to: size
I'm parsing XML files from an in-memory ZIP Archive and had some real
problem with non-ASCII characters. Took m
