On 06 Nov 2013, at 13:59, Sven Van Caekenberghe s...@stfx.eu wrote:
On 06 Nov 2013, at 13:29, Henrik Johansen henrik.s.johan...@veloxit.no
wrote:
On 06 Nov 2013, at 10:38 , Sven Van Caekenberghe s...@stfx.eu wrote:
BTW, do we still need UTF16 support ?
For those encodings that we
On 04 Nov 2013, at 17:12, Sven Van Caekenberghe s...@stfx.eu wrote:
Hi Henrik,
Great writeup, thanks !
(more inline)
On 04 Nov 2013, at 11:58, Henrik Johansen henrik.s.johan...@veloxit.no
wrote:
On 04 Nov 2013, at 9:57 , Diego Lont diego.l...@delware.nl wrote:
Working on Petit
On 04 Nov 2013, at 22:25, Henrik Sperre Johansen henrik.s.johan...@veloxit.no
wrote:
That's great!
Remembering that commit message was part of the reason for benching, was sort
of disappointed there was no significant difference between Zn in 2.0 and
latest 3.0...
I guess with the
On 04 Nov 2013, at 5:12 , Sven Van Caekenberghe s...@stfx.eu wrote:
Well, I just realised that ZnCharacterReadStream and ZnCharacterWriteStream
did not yet make use of the optimisations that I did for ZnCharacterEncoding
some time ago. More specifically, they were not yet using
On 06 Nov 2013, at 10:38 , Sven Van Caekenberghe s...@stfx.eu wrote:
BTW, do we still need UTF16 support ?
For those encodings that we still want to support in the future, we should
have new and more principled implementations under ZnCharacterEncoder. That
is, if we ever want to fase out
Hi henrik
why don't you give a try to change our lives and propose a new
MultuByteFileStream and friends :)
Stef
That's great!
Remembering that commit message was part of the reason for benching, was sort
of disappointed there was no significant difference between Zn in 2.0 and
latest
BTW, do we still need UTF16 support ?
For those encodings that we still want to support in the future, we should
have new and more principled implementations under ZnCharacterEncoder. That
is, if we ever want to fase out TextConverter.
:)
You know what I think.
Kill all the rotten
that would be called XStreams, no?
On 2013-11-06, at 13:43, Stéphane Ducasse stephane.duca...@inria.fr wrote:
Hi henrik
why don't you give a try to change our lives and propose a new
MultuByteFileStream and friends :)
Stef
That's great!
Remembering that commit message was part of
On 06 Nov 2013, at 13:20, Henrik Johansen henrik.s.johan...@veloxit.no wrote:
On 04 Nov 2013, at 5:12 , Sven Van Caekenberghe s...@stfx.eu wrote:
Well, I just realised that ZnCharacterReadStream and ZnCharacterWriteStream
did not yet make use of the optimisations that I did for
On 06 Nov 2013, at 13:29, Henrik Johansen henrik.s.johan...@veloxit.no wrote:
On 06 Nov 2013, at 10:38 , Sven Van Caekenberghe s...@stfx.eu wrote:
BTW, do we still need UTF16 support ?
For those encodings that we still want to support in the future, we should
have new and more
Hi Diego,
Streams as they are currently defined, especially ReadStreams, can hardly be
called IO streams. Many operations assume that there is a single collection
over which you can move in any direction without restrictions. As a consequence
most parsing code relies this ability, looking
On 04 Nov 2013, at 9:57 , Diego Lont diego.l...@delware.nl wrote:
Working on Petit Delphi we found a strange implementation for asPetitStream:
StreamasPetitStream
^ self contents asPetitStream
Further investigation showed that the basic peek was not fast enough for
Petit Parser, as
Hi Henrik,
Great writeup, thanks !
(more inline)
On 04 Nov 2013, at 11:58, Henrik Johansen henrik.s.johan...@veloxit.no wrote:
On 04 Nov 2013, at 9:57 , Diego Lont diego.l...@delware.nl wrote:
Working on Petit Delphi we found a strange implementation for asPetitStream:
StreamasPetitStream
That's great!
Remembering that commit message was part of the reason for benching, was
sort of disappointed there was no significant difference between Zn in 2.0
and latest 3.0...
I guess with the amount of hacks accumulating, it is indeed turning into a
worthy successor of MultiByteFileStream ;)
14 matches
Mail list logo
