Bug - Parsing issue

[woobs]

My bad I should have asked for your .ini first. It was bad timing with the parser changes and the prior issues.

Thank you, everyone!

 

[Knightly]

My bad I should have asked for your .ini first. It was bad timing with the parser changes and the prior issues.

Thank you, everyone!

No worries, it happens. If you do have parser issues, from my side it's helpful to know what your expected output is versus the actual output so I can troubleshoot what's going on. With the reversion of the brace handler and removal of escape characters, the updates to noparse, and the changes in if processing -- it should be 100% backwards compatible.

I've run it through most of the macros that I can find, including complex ones like kiss and core and every time I've found an issue or someone has reported an issue I have a list of test cases that I add that to in order to make sure that I don't accidentally reintroduce that bug. Even with those test cases, my process is I run through the standard set of macros to see if I can find a problem. As of the release that's on RG, there have been no reported errors or differences in the parser (other than the intended ones with the additional functionality), but that doesn't mean that there's not something out there that I missed.

I'm happy to troubleshoot any issues, but at this point I think the parser is stable and what's going to come out are going to be edge cases that rarely (if ever) got used. Still, it's possible so please continue to let me know if you think there's a parsing issue (expected output vs actual output).