When "getNextBlock" was called after "getNextLine", the pointer could still on the newline.

Browse Source

The pointer to a newline could not advance enough, when the line ended with \r\n. The resulting buffer was correct, as the buffer range went from <start> until \r, but that the pointer increased by just 1 could lead to the problem that the next pointer points at \n, which is still part of the newline and therefore, "getNextBlock" got 1 byte too much.

Refs Issue #4871

...

This commit is contained in:

Matthias Möller

2023-02-04 15:16:22 +01:00

parent 8c6b3fe69a

commit db72c6ee38

4 changed files with 19 additions and 1 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

test/models/PLY/cube_binary_header_with_RN_newline.ply

BIN

Binary file not shown.