René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Interpreting LoadObj return value -- strict OBJ specification","articleBody":"I've encountered an issue when using `LoadObj` to parse a file. Specifically, what happens when the wrong file type is provided to the parser. In this case, `LoadObj` doesn't return an error, it simply leaves the vector of `shape_t` empty.\r\n\r\nThe reason for this, based on a coarse once over on the code, is that the parsing takes an XML-like approach. It looks for specific tokens at the beginning of lines (e.g., `f`, `v`, `vt`, etc.) If it finds such a token and the remainder of the line is not consistent with what it expects to see, it returns false. However, if it finds no such token at the beginning of the line, the line is *simply ignored*. Thus, if I were to pass an STL file into `LoadObj`, the parsing would report \"success\", but give me empty geometry.\r\n\r\nIf we applied a stricter interpretation of the Obj spec, a line that isn't strictly valid OBJ and isn't commented out should produce an error as being malformed for an OBJ file. This would give us a greater power to distinguish the output of `LoadObj`.\r\n\r\nI'm willing to submit a PR in this regard -- but I want to gauge the interest of the set of users in this regard.","author":{"url":"https://github.com/SeanCurtis-TRI","@type":"Person","name":"SeanCurtis-TRI"},"datePublished":"2020-03-30T14:35:52.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/272/tinyobjloader/issues/272"}