Files
assimp/code/AssetLib
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
..
2023-01-16 21:47:11 +01:00
2023-01-16 21:47:11 +01:00
2022-12-05 13:15:42 +01:00
2023-01-16 09:12:35 +01:00
2023-01-16 09:12:35 +01:00
2023-01-16 09:12:35 +01:00
2023-01-16 08:18:36 +01:00
2023-01-16 21:47:11 +01:00
2023-01-16 09:12:35 +01:00
2023-01-16 09:12:35 +01:00
2023-01-16 09:12:35 +01:00
2022-08-25 11:32:59 -04:00
2023-01-16 09:12:35 +01:00
2023-01-16 09:12:35 +01:00
2023-01-16 08:12:24 +01:00
2022-09-02 11:20:02 -04:00
2023-01-16 09:12:35 +01:00
2022-01-10 21:13:43 +01:00
2023-02-03 11:44:27 +02:00
2023-01-16 08:18:36 +01:00