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
gie: implement a strict mode with <gie-strict> </gie-strict> (fixes #2158) #2168
Conversation
7d446e1
to
7747de8
Compare
7747de8
to
cde1a5d
Compare
I have no strong feelings around this, although I probably would have preferred the syntax I proposed in #2158: If I understand your proposed syntax correctly, the strictness may shift half way through the input file (in which case, I believe there should also be a way to switch back to lax mode again). Anyway - most important to me is to keep the original syntax as the default, as it really is quite useful in its own right, as demonstrated in the PROJ teaching material, I linked to over in #2158. |
cde1a5d
to
66c2ccf
Compare
ah sorry I missed that part, and was actually thinking about something similar. Just pushed this |
Groovy :-) |
…SGeo#2158) In that mode: * All non-comment/decoration lines must start with a valid tag * Commands split on several lines should be terminated with " \"
66c2ccf
to
4745842
Compare
All .gie files converted and documentation added in gie.rst. There were a few instances of misspelled |
Just got feedback from @ccrook that he also got hit by expect/except misspelling, so I see a great future for |
In that mode:
@busstoptaktik @kbevers Before I make the effort of converting all gie files in test/gie/ with those rules, I want to have your blessing