You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the beginning of resinator, there was 1 parsing algorithm used for string literals. Since then, that has been split many times into multiple specialized parsers for different things:
"Normal" string parsing
DLGINCLUDE strings
Accelerators
parseQuotedStringAsWideString
Maybe more I'm forgetting right now
Recently, though, these implementations have been re-converging as I find new edge cases and make corrections. For example, accelerator string parsing and parseQuotedStringAsWideString are now roughly equivalent, but they are still using separate implementations.
It's possible that there's some commonality between all of the different implementations that I'm missing that would allow them to converge even further.
The text was updated successfully, but these errors were encountered:
In the beginning of
resinator
, there was 1 parsing algorithm used for string literals. Since then, that has been split many times into multiple specialized parsers for different things:DLGINCLUDE
stringsRecently, though, these implementations have been re-converging as I find new edge cases and make corrections. For example, accelerator string parsing and
parseQuotedStringAsWideString
are now roughly equivalent, but they are still using separate implementations.It's possible that there's some commonality between all of the different implementations that I'm missing that would allow them to converge even further.
The text was updated successfully, but these errors were encountered: