Matthias Möller db72c6ee38 When "getNextBlock" was called after "getNextLine", the pointer could still on the newline. ... 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		2023-02-04 15:16:22 +01:00
..
PlyExporter.cpp	Manually fix up 100 more instances where it should be defaulted	2022-08-25 12:20:13 -04:00
PlyExporter.h	Update copyrights	2022-01-10 21:13:43 +01:00
PlyLoader.cpp	Apply various clang-tidy checks for smartprs and modern C++ types	2022-11-08 11:03:55 -05:00
PlyLoader.h	Update copyrights	2022-01-10 21:13:43 +01:00
PlyParser.cpp	When "getNextBlock" was called after "getNextLine", the pointer could still on the newline.	2023-02-04 15:16:22 +01:00
PlyParser.h	Tidy Up Constructors and Destructors	2023-01-16 21:47:11 +01:00