Verify that v3.8 features require #version 3.8
#420
Labels
cleanup
miscellaneous housekeeping
Milestone
Comments
c-lipka
added a commit
that referenced
this issue
Jul 11, 2021
- Addresses issue #420 - POV-Ray will now warn when using v3.7 or v3.8 features without matching `#version` directive. - For consistency, POV-Ray will no longer throw an error whenever encountering anything macro-related in v3.0 scenes, and instead just warn when encountering `#macro` in such scenes. - Modified internal tracking of scene language version to use a dedicated class instead of an `int`. - Added a framework to print certain warnings only once.
trevorsandy
pushed a commit
to trevorsandy/povray
that referenced
this issue
Jul 18, 2021
- Addresses issue POV-Ray#420 - POV-Ray will now warn when using v3.7 or v3.8 features without matching `#version` directive. - For consistency, POV-Ray will no longer throw an error whenever encountering anything macro-related in v3.0 scenes, and instead just warn when encountering `#macro` in such scenes. - Modified internal tracking of scene language version to use a dedicated class instead of an `int`. - Added a framework to print certain warnings only once.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Unless
#version 3.8is specified, any v3.8 features should either be disabled (if automatic) or trigger a warning (if requiring extra syntax), so that the user doesn't accidently mark a scene as v3.7 compatible that actually requires v3.8 to render as intended.It needs to be verified that this is true for all v3.8 features.
It also should be douible-checked that the equivalent is true for all v3.7 features unless
#version 3.7or above is specified.The text was updated successfully, but these errors were encountered: