forked from increpare/PuzzleScript
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Generalize code for the two syntaxes defining expansions #56
Labels
code
Improve the code without changing functionality
console messages
Content and presentation of compilation errors/warnings and other console messages
debugging
features to help designers understand the engine's behavior
editor
Concerns the game editor
expansion
any expansion mechanism
mappings
Anything that concerns mappings
sprite manipulations
copying and transforming sprites
syntax/language
Concerns the language or its syntax
Milestone
Comments
TODO:
|
ClementSparrow
added
syntax/language
Concerns the language or its syntax
sprite manipulations
copying and transforming sprites
mappings
Anything that concerns mappings
labels
Aug 8, 2022
Identifier-defined
Parameters-defined
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
code
Improve the code without changing functionality
console messages
Content and presentation of compilation errors/warnings and other console messages
debugging
features to help designers understand the engine's behavior
editor
Concerns the game editor
expansion
any expansion mechanism
mappings
Anything that concerns mappings
sprite manipulations
copying and transforming sprites
syntax/language
Concerns the language or its syntax
Currently, there are two syntaxes to introduce new expansion contexts:
LEGEND
section, the tag classes used in the object name define an expansion context.COLLISIONLAYERS
andRULES
sections, when we list known properties and tag classes before a->
.Common code should be written for all the occurrances of each syntax so that we can easily reuse the syntax to add expansion mechanisms elsewhere (including new features of the engine). The code should be able to manage some of the features needed for parsing the syntax that introduces the expansion context, and some of the features needed to use the expansion context (i.e., check if a specific expansion makes sense in that context, compute the expansion, and log errors).
The text was updated successfully, but these errors were encountered: