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
Certain aggregate symbols cause problems in other aggregates #203
Comments
|
not sure if this is a bug or a feature special symbols can't be used to refer to objects in the rules section, so maybe just a better error message? ("objects can only be referred to by symbols in the levels section") |
|
i guess you should be allowed to refer to things by symbols/their names On Mon, Sep 1, 2014 at 4:04 AM, Ryan Hitchman notifications@github.com
|
|
need to do #375 first - the system right now can't handle chains of definitions, so even if I allow the compiler to parse this it will get confused. |
|
So I thought about this, and I managed to implement support for it that didn't break the tests. However, I feel like it's not something I want to support? The small but definite chance of this change randomly breaking someone's game isn't maybe worth allowing people to code in a coding style I'm not too hot for - the randomo symbols are enabled chiefly for the map editor. I just see lots of nasty edge cases coming up if I add this feature and anyone actually uses it. So better that people encounter errors sooner rather than later ^^ (but a better error message may be nice) ( ) |

ben-reilly commentedMay 7, 2014
Somewhat similar to #202 (and by extension, #128), special symbols seem to not be parsed properly when used in an aggregate.
e.g.
gives the error
The text was updated successfully, but these errors were encountered: