New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.seek(... SeekFromCurrent) seeks to incorrect place if called after .readchars #6074
Comments
From @zoffixznetIf .seek(... SeekFromCurrent) is called after a call to .readchars, the position sought to appears to be way off target: 22:54 IOninja m: "/tmp/Foo.pm6".IO.spurt: "I love you so very much"; with "/tmp/Foo.pm6".IO.open { .read(2); .seek: 1, SeekFromCurrent; .tell.say } After some discussion on IRC (https://irclog.perlgeek.de/perl6-dev/2017-02-22 ), one suggestion was that there's some sort of buffering involved: 23:00 m: "/tmp/Foo.pm6".IO.spurt: "I love you\nso very much"; with "/tmp/Foo.pm6".IO.open { .readchars(2); .seek: 1, SeekFromCurrent; .tell.say } This behaviour is not present on JVM. |
From @dogbert17On Wed, 22 Feb 2017 15:09:44 -0800, cpan@zoffix.com wrote:
The fixes, and tests, made by Zoffix, when fixing https://rt.perl.org/Public/Bug/Display.html?id=131376 |
The RT System itself - Status changed from 'new' to 'open' |
@dogbert17 - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#130843 (status was 'resolved')
Searchable as RT130843$
The text was updated successfully, but these errors were encountered: