Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Colons seem to throw the parser off #28

Closed
InfiniteAmmoInc opened this issue Feb 28, 2016 · 2 comments
Closed

Colons seem to throw the parser off #28

InfiniteAmmoInc opened this issue Feb 28, 2016 · 2 comments

Comments

@InfiniteAmmoInc
Copy link
Collaborator

<<if $germ_home_quest is 0>>
    [[HomeQuestIntro]]
<<elseif $germ_home_quest is 1>>
    [[HomeQuestTrampoline]]
<<endif>>

<<if $germ_home_quest > 0>>
    <<hide Collision:GermOnPorch>>
<<endif>>

The parser fails on the last line. I'm seeing the same thing happening in other files that where ":" is used in a command line etc.

@desplesda
Copy link
Collaborator

Looks like it's not just colons - this fails to parse too:

<<!@#$%^&*()⁄€‹›fifl‡°·‚‘-=_+>>

Looking at what the parser is doing, it's successfully reading the << token, then hide but then reads Collision:GermOnPorch>>. It then doesn't find the >>, because that just got read, and ends up confused.

desplesda added a commit that referenced this issue Feb 28, 2016
@desplesda
Copy link
Collaborator

Ok, I've fixed it for the specific case of colons, but not for the general case of arbitrary punctuation. That'll have to wait until later.

Source package is attached.

YarnSpinner-0.9.7.2-1-gbb71920-development-source-minimal.unitypackage.zip

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants