Dear developers,

I have filed a bug report #1651 Stream I/O "read shared" and "read shared 
nobuffer" behaves differently for strings of 512 bytes or longer, I can now 
reproducibly confirm that opening a stream as "read shared nobuffer“ will lose 
one character (the 512th) in the read for any string longer than 512 characters.

I think someone needs to look into this, maybe it is the source of the three 
failing test cases.

For what it is worth  "read shared“ works for the same string, also if it goes 
beyond 512 characters

P.O. Jonsson

> Am 25.09.2019 um 22:18 schrieb P.O. Jonsson <>:
> Dear Enrico,
> I have noticed this as well, it has been going on for some time I think. 
> Tests fail on all platforms and the 3 you mention are, I think, related to 
> the first one
> TEST_LINEIN_BUG1472 in  Stream.testGroup
> I looked a bit at it yesterday, thinking (hoping) it might only be the test 
> cases that needed „fixing“ after the bug was fixed, but I think the problem 
> resides in the stream class itself, and how it is implemented, look in the 
> test case for info.
> I noticed that the test string for TEST_LINEIN_BUG1472 testcase contained 
> characters and whitespace when it failed. When I replaced this with only text 
> (no cr lf or .endofline etc) the test case passed. So my guess is that there 
> is still some problem with storing character strings in the stream class. It 
> would explain the other test cases failing as well.
> @developers: Do you want me to file a bug report or is this sufficient info?
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> <>
>> Am 25.09.2019 um 17:11 schrieb Enrico Sorichetti via Oorexx-devel 
>> < 
>> <>>:
>>   Class:  Stream.testGroup
> _______________________________________________
> Oorexx-devel mailing list

Oorexx-devel mailing list

Reply via email to