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 an ideal case, we would like to allow any style of comments legal in a language's syntax to be used to mark the stub and solution blocks in exercise templates.
For this to be possible, the language plugins must supply the template parser with information on what kind of comment strings to except. So for Java, accept comments of type // .. and /* .. */, and for python accept comments of type # .. and """\n .. \n""".
The parser should be adapted to retrieve information of possible start and end symbols from a language plugin and then parse the exercise template based on those.
The text was updated successfully, but these errors were encountered:
Where in language plugin should this information be provided in? I can work on this, but I'd like to get some more info on what is required on the plugins side.
I suspect the most preferable way to implement this is by building all the logic in tmc-langs-framework and then only have the comment tokens / regexes / whatevers in the specific plugins. Actual implementation details are left to the coder.
This issue depends on #25.
In an ideal case, we would like to allow any style of comments legal in a language's syntax to be used to mark the stub and solution blocks in exercise templates.
For this to be possible, the language plugins must supply the template parser with information on what kind of comment strings to except. So for Java, accept comments of type
// ..
and/* .. */
, and for python accept comments of type# ..
and"""\n .. \n"""
.The parser should be adapted to retrieve information of possible
start
andend
symbols from a language plugin and then parse the exercise template based on those.The text was updated successfully, but these errors were encountered: