Files
assimp/test/models
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
..
2018-09-21 16:09:24 +02:00
2018-11-21 21:39:16 +01:00
2022-05-13 19:44:14 +02:00
2021-10-07 10:01:32 +01:00
2013-10-12 20:10:38 +02:00
2021-12-18 15:34:58 +03:00
2019-05-24 17:22:54 +02:00
2019-11-01 17:21:24 +01:00
2018-07-11 11:09:53 +02:00
2018-09-17 18:48:14 +02:00
2020-03-30 20:33:43 +02:00
2021-11-10 20:37:27 +01:00