|
 |
Is it advisable to go through my include files and update them to version 3.7?
Is it a good idea to set the #version to 3.7 even if no changes are required?
I noticed that all the standard include files in the 3.7 release still have
#version 3.5, so the answer to my questions would *seem* to be "no," but I would
like to know what people think.
Post a reply to this message
|
|
|
|
Cousin Ricky <ric### [at] yahoo com> wrote:
> Is it advisable to go through my include files and update them to version 3.7?
> Is it a good idea to set the #version to 3.7 even if no changes are required?
Note that POV-Ray 3.7 will behave differently depending on whether #version
has been set to 3.6 or 3.7, at least when talking about gamma correction.
(I don't remember now, however, what happens if the main pov file has a
#version 3.6 or no explicit #version, and an include file has #version 3.7...)
--
- Warp
Post a reply to this message
|
|
|
|
Am 19.07.2011 04:41, schrieb Cousin Ricky:
> Is it advisable to go through my include files and update them to version 3.7?
> Is it a good idea to set the #version to 3.7 even if no changes are required?
>
> I noticed that all the standard include files in the 3.7 release still have
> #version 3.5, so the answer to my questions would *seem* to be "no," but I would
> like to know what people think.
I think the standard include files do it right:
- To prevent overriding the #version requested by the main file, start
and end the include file with something like
#local FOO = version;
#version 3.5;
// ...
// file content proper
// ...
#version FOO;
- In the #version statement, use the lowest version number that is known
to work with your include file, in order to provide backward compatibility.
Post a reply to this message
|
|
