-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
REM and ENDREM as comment blocks #83
Comments
MBCONST static const char _MULTI_LINE_COMMENT_PREFIX[] = "'REM";
MBCONST static const char _MULTI_LINE_COMMENT_POSTFIX[] = "'ENDREM"; to use
c == _MULTI_LINE_COMMENT_PREFIX[context->multi_line_comment_count++]
...
c == _MULTI_LINE_COMMENT_POSTFIX[context->multi_line_comment_count++] to toupper(c) == _MULTI_LINE_COMMENT_PREFIX[context->multi_line_comment_count++]
...
toupper(c) == _MULTI_LINE_COMMENT_POSTFIX[context->multi_line_comment_count++] for case-insensitive.
static bool_t _is_comment_char(char c) {
return (c == '\'') || (c == '#');
} to use |
Thanks, but I was aiming for not using symbols before the keyword for this change so without ' or # just plain |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I thought it would be more consistent to just use
REM
andENDREM
as comment blocks instead of '[ and '] which looks more like arrays. The syntax already has REM as a single line comment.If there's no plan to change this, perhaps you could provide some pointers on how to do this update.
Reference:
https://picaxe.com/basic-commands/directives/hash-endrem/
The text was updated successfully, but these errors were encountered: