Bug 24557 – File.readln does not properly handle case where last character in terminator is repeated

Status
NEW
Severity
normal
Priority
P1
Component
phobos
Product
D
Version
D2
Platform
All
OS
All
Creation time
2024-05-20T14:01:52Z
Last change time
2024-12-01T16:42:34Z
Assigned to
No Owner
Creator
zopsicle
Moved to GitHub: phobos#10551 →

Comments

Comment #0 by zopsicle — 2024-05-20T14:01:52Z
Consider the following program: ----- import std.stdio : readln, writefln; void main() { char[] buf; readln(buf, "ABA"); writefln!"%(%s%)"([buf]); } ----- Compiled and run as follows: ----- $ dmd example.d $ printf 'XABAY' | ./example ----- Expected output: "XABA" Actual output: "XABAY" readln does not properly handle the case where the last character of the terminator (in this case A) appears multiple times in the terminator (in this case, A also appears at the front of the terminator).
Comment #1 by schveiguy — 2024-05-20T17:38:51Z
readln does use the last character, but it is also validating the "line" ends in the full termination sequence. However, the bug is that if the last character is repeated in the termination sequence, it checks just the new data that it has read for the termination sequence. So for example, if you look for `ging` as the termination sequence, the following algorithm results (assume input is `bringing home the bacon`): 1. result = "", readln('g') => "bring". Does "bring" end in "ging"? no 2. result = "bring", readln('g') => "ing". Does "ing" end in "ging"? no 3. result = "bringing", readln('g') => " home the bacon". readln returned no delim found, so result is "bringing home the bacon" Instead, readln should check the *concatenated* result (but obviously, only the result that has been appended since the readln call was started.
Comment #2 by robert.schadek — 2024-12-01T16:42:34Z
THIS ISSUE HAS BEEN MOVED TO GITHUB https://github.com/dlang/phobos/issues/10551 DO NOT COMMENT HERE ANYMORE, NOBODY WILL SEE IT, THIS ISSUE HAS BEEN MOVED TO GITHUB