Hi Nicolas,

You have been working quite quickly, great!

I tried to follow your different releases in Pharo 1.1.1, right now I have 433 tests, 3 failures (#testReadWriteLargeAmount), 11 errors (#..base64 and #..multipleBufferSize). If will send you the report.

I have been trying some of the examples from the doc pages (google code project), this simple one still fails:

((1 to: 10) reading collecting: [:x | x * x]) rest

The readline example is using the non-existing #slicer: method, this simpler version seems to work:

|text|
text := 'line1\line2\line3\line4' withCRs reading.
text := text ender: [ :char | char = Character cr ].
text collect: [ :line | line rest ].

That is a documentation bug though.

Sven


On 10 Oct 2010, at 22:09, Nicolas Cellier wrote:

> Hi again,
> I now have ported two more packages
> - Xtreams-Transforms
> - Xtreams-Substreams
> and their tests
> 
> I did not have any portability problem with those...
> But that's because I did not handle the Character encoder/decoder.
> Consequently, I have 8 tests failing (the Base64 related tests)
> Plus 4 other tests failing because of my poor implementation of
> #after:do: (forking processes in a SUnit TestCase can't be that
> obvious).
> 
> Now, the easy part of the port (copy/paste) is almost ended.
> Once we manage a compatible way to handle pragmas, PEG Parser should
> port quite easily too.
> 
> Then, the harder work begins:
> - File/Socket/Pipe
> - Pointers (in External Heap)
> - Character encoding/decoding
> - Compression/Decompression
> 
> If you think you can help in any of these, please tell.
> 
> Nicolas
> 
> _______________________________________________
> Pharo-project mailing list
> Pharo-project at lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project