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
We have some pointer semantics that break when the parser thinks a keyword in a n include file has not ended but the file has. It will happily read the next line in the outer file and hell (a segmentation fault with the usual non-user-friendly error message) will break loose.
Noticed on an include file where the last non-whitespace entry was a backslash instead of a sleash.
T.B.C
The text was updated successfully, but these errors were encountered:
We have some pointer semantics that break when the parser thinks a keyword in a n include file has not ended but the file has. It will happily read the next line in the outer file and hell (a segmentation fault with the usual non-user-friendly error message) will break loose.
Noticed on an include file where the last non-whitespace entry was a backslash instead of a sleash.
T.B.C
The text was updated successfully, but these errors were encountered: