Closed dazinator closed 6 years ago
Discovered whilst investigating #46
When setting the following:
options.Parsing.AllowInvalidPathCharacters = true;
and tokenising **/foo/
**/foo/
It causes the tokeniser to parse the literal foo as foo/. This causes a literal match on the path seperator which is problematic if mixed slashes are used.
foo
foo/
Discovered whilst investigating #46
When setting the following:
and tokenising
**/foo/It causes the tokeniser to parse the literal
fooasfoo/. This causes a literal match on the path seperator which is problematic if mixed slashes are used.