Reference:Version Directive - Revision history

Clipka: Removed description of v3.8 behavior (error on late `#version 3.8` statement) that will be rolled back and not be present in v3.8.0 proper.

2021-06-21T11:58:33Z

Removed description of v3.8 behavior (error on late `#version 3.8` statement) that will be rolled back and not be present in v3.8.0 proper.

Jholsenback: clarity

2018-10-02T09:43:49Z

clarity

Jholsenback: changes from talk page

2018-10-01T00:04:52Z

changes from talk page

Jholsenback: minor update

2018-02-10T19:33:13Z

minor update

Jholsenback: minor

2017-06-26T11:07:18Z

minor

Jholsenback: version changes

2017-06-26T10:13:39Z

version changes

Jholsenback: added {{Change}} notation

2016-12-31T19:53:39Z

added {{Change}} notation

Clipka: indexentry fix

2016-05-03T23:34:38Z

indexentry fix

Clipka: Update for 3.7.1

2016-01-26T06:18:50Z

Update for 3.7.1

Jholsenback: link repair

2012-03-15T19:45:25Z

link repair

@@ Line 14: / Line 14: @@
 <p>There must be a semi-colon after the float expression in a <code>#version</code> directive. If omitted a warning is generated and some macros may not work properly. Additionally you may use the <code>Version=</code><em>n.n</em> option or the <code>+MV</code><em>n.n</em> switch to establish the <em>initial</em> setting. For example, the parsing of float expressions was introduced in version 2.0 and it was incompatible with <em>any</em> version 1.0 scene file. Using <code>#version 1.0</code> turns off expression parsing as well as many warning messages so that nearly all 1.0 files will still work. Some obsolete or re-designed features <em>are totally unavailable in the current version of POV-Ray REGARDLESS OF THE VERSION SETTING.</em> Details on these features are noted throughout this documentation.</p>
-<p>As of version 3.7 the following <em>requirement</em> has been implemented. In order to obtain full version 3.7 functionality you <em>MUST</em> specify the <code>#version 3.7;</code> directive in your scene file. Prior to a <code>#version</code> directive appearing the version defaults to 3.62. Additionally, if the first <code>#version</code> directive appears after any other declaration, or a <code>#version</code> directive does not appear at all a post-parse warning is issued. A {{Change}} as of POV-Ray 3.8 now makes it an outright error to use <code>#version 3.8;</code> or higher in a main scene file that does not start with a <code>#version</code> directive.</p>
+<p>As of version 3.7 the following <em>requirement</em> has been implemented. In order to obtain full version 3.7 functionality you <em>MUST</em> specify the <code>#version 3.7;</code> directive in your scene file. Prior to a <code>#version</code> directive appearing the version defaults to 3.62. Additionally, if the first <code>#version</code> directive appears after any other declaration, or a <code>#version</code> directive does not appear at all a post-parse warning is issued.</p>
 <p>New defaults require that the language version is explicitly set to 3.8 or higher via the <code>#version</code> directive the <code>Version=</code>n.n INI setting or the <code>+MV</code>n.n command-line option. Otherwise POV-Ray will fall back to legacy defaults for backwards compatibility.</p>

@@ Line 36: / Line 36: @@
 <p>As previously mentioned the <code>#version</code> directive can be used to switch back and forth between the defaults as long as no explicit <code>#default</code> directive statement is specified. However, as soon as the first <code>#default</code> directive is encountered, any subsequent <code>#version</code> directives that would normally affect the defaults will instead just generate a warning.</p>
-<p>Consider the following examples:</p>
+<p>Consider the following examples in their entirety:</p>
 <pre>

@@ Line 3: / Line 3: @@
 {{#indexentry:#version}}
 {{#indexentry:version}}
-<p>As POV-Ray has evolved from version 1.0 through 3.8 we have made every effort to maintain some amount of backwards compatibility with earlier versions. Some old or obsolete features can be handled directly without any special consideration by the user. Some old or obsolete features can no longer be handled at all. However <em>some</em> old features can still be
+<p>Since POV-Ray has evolved over the years from version 1.0 through 3.8 we have made every effort to maintain some amount of backwards compatibility with earlier versions. Some old or obsolete features can be handled directly without any special consideration by the user. Some old or obsolete features can no longer be handled at all. However <em>some</em> old features can still be used if you alert POV-Ray that this is an older scene. The <code>#version</code> directive can be used to switch version compatibility or change default settings several times throughout a scene file.</p>
-used if you warn POV-Ray that this is an older scene. The <code>#version</code> directive can be used to switch version compatibility to different setting several times throughout a scene file. The syntax is:</p>
 <pre>
 VERSION_DIRECTIVE:
    #version FLOAT;
 </pre>
-<p class="Note"><strong>Note:</strong> There should be a semi-colon after the float expression in a <code>#version</code> directive. This semi-colon is introduced in POV-Ray version 3.1. If omitted, it generates a warning and some macros may not work
-properly.</p>
+<p>There must be a semi-colon after the float expression in a <code>#version</code> directive. If omitted a warning is generated and some macros may not work properly. Additionally you may use the <code>Version=</code><em>n.n</em> option or the <code>+MV</code><em>n.n</em> switch to establish the <em>initial</em> setting. For example, the parsing of float expressions was introduced in version 2.0 and it was incompatible with <em>any</em> version 1.0 scene file. Using <code>#version 1.0</code> turns off expression parsing as well as many warning messages so that nearly all 1.0 files will still work. Some obsolete or re-designed features <em>are totally unavailable in the current version of POV-Ray REGARDLESS OF THE VERSION SETTING.</em> Details on these features are noted throughout this documentation.</p>
-<p>Additionally you may use the <code>Version=</code><em>n.n</em> option or the <code>+MV</code><em>n.n</em> switch to establish the <em>initial</em> setting. See <!--<linkto "Language Version">Language Version</linkto>--->[[Reference:Scene Parsing Options#Language Version|Language Version]] for details. For example, one feature introduced in 2.0 that was incompatible with any 1.0 scene files is the parsing of float expressions. Using <code>#version 1.0</code> turns off expression parsing as well as many warning messages so that nearly all 1.0 files will still work.</p>
-<p class="Note"><strong>Note:</strong> Some obsolete or re-designed features <em>are totally unavailable in the current version of POV-Ray REGARDLESS OF THE VERSION SETTING.</em> Details on these features are noted throughout this documentation.</p>
+<p>As of version 3.7 the following <em>requirement</em> has been implemented. In order to obtain full version 3.7 functionality you <em>MUST</em> specify the <code>#version 3.7;</code> directive in your scene file. Prior to a <code>#version</code> directive appearing the version defaults to 3.62. Additionally, if the first <code>#version</code> directive appears after any other declaration, or a <code>#version</code> directive does not appear at all a post-parse warning is issued. A {{Change}} as of POV-Ray 3.8 now makes it an outright error to use <code>#version 3.8;</code> or higher in a main scene file that does not start with a <code>#version</code> directive.</p>
 <p>The built-in float identifier <code>version</code> contains the current setting of the version compatibility option. See
-Float Expressions: [[Reference:Numeric Expressions#Built-in Variables|:Float, built-in variables|Built-in Variables]]. Together with the built-in <code>version</code> identifier the <code>#version</code> directive allows you to save and restore the previous values of this compatibility setting. The new <code>#local</code> identifier option is especially useful here. For example, suppose <code>mystuff.inc</code> is in version 3.5 format. At the top of the file you could put:</p>
+<p>New defaults require that the language version is explicitly set to 3.8 or higher via the <code>#version</code> directive the <code>Version=</code>n.n INI setting or the <code>+MV</code>n.n command-line option. Otherwise POV-Ray will fall back to legacy defaults for backwards compatibility.</p>
 <pre>
    #local Temp_Vers = version;  // Save previous value
@@ Line 22: / Line 32: @@
 </pre>
-<p>As of version 3.7, there has been a <em>requirement</em> implemented. In order to obtain full version 3.7
+<p class="Note"><strong>Note:</strong> In version 3.7, if the version compatibility option was left at its default, the <code>version</code> identifier evaluated to the actual POV-Ray version number, instead of matching the defaulted version compatibility setting of 3.62. This would cause problems with include files using the above construct, as it would inadvertently switch the compatibility setting from 3.62 to 3.7. This has been fixed by a {{Change}} in version 3.8, where the <code>version</code> identifier matches the version compatibility option default in such a situation. There is still one exception to this rule: If the scene starts with a <code>#version</code> directive, and the <code>version</code> identifier is used in that directive, it will default to the actual POV-Ray version number in that very first statement, so that the <code>#version version;</code> idiom can still be used.</p>
-functionality, you <em>MUST</em> specify the <code>#version 3.7</code> directive in your scene file. Prior to a
-<code>#version</code> directive appearing, the version defaults to 3.62. Additionally, if the first <code>#version</code>
+<p>As previously mentioned the <code>#version</code> directive can be used to switch back and forth between the defaults as long as no explicit <code>#default</code> directive statement is specified. However, as soon as the first <code>#default</code> directive is encountered, any subsequent <code>#version</code> directives that would normally affect the defaults will instead just generate a warning.</p>
-appears after any other declaration, or a <code>#version</code> directive does not appear at all,
-a post-parse warning is issued, and a {{Change}} as of POV-Ray 3.8 or later it is now considered an outright error to use
+<p>Consider the following examples:</p>
-<code>#version 3.8</code> or higher in a main scene file that does not start with a <code>#version</code> directive.</p>
 <pre>
-   #version version;
+   #version 3.7;
 </pre>
-<p class="Warning"><strong>Warning:</strong> The version directive and command-line setting no longer provide compatibility with most rendering bugs in versions prior to POV-Ray 3.5. However, compatibility with the scene language is provided for scenes as old as POV-Ray 1.0 just as in all previous versions of POV-Ray. Nevertheless, we strongly recommend you update scenes at least to POV-Ray 3.7 syntax if you plan to use them in future versions of POV-Ray.</p>
+<p>The <code>#version</code> directive just generates a warning because the earlier <code>#default</code> directive has <em>locked</em> the version 3.8 defaults overriding the pigment in the process. If <em>OtherTexture</em> does not explicitly specify an ambient value, it will also have an ambient value of zero.</p>

← Older revision		Revision as of 19:33, 10 February 2018
Line 39:		Line 39:
	version compatibility option anywhere else.		version compatibility option anywhere else.

−	<p class="Warning"><strong>Warning:</strong> The version directive and command-line setting no longer provide compatibility with most rendering bugs in versions prior to POV-Ray 3.5. However, compatibility with the scene language is provided for scenes as old as POV-Ray 1.0 just as in all previous versions of POV-Ray. Nevertheless, we strongly recommend you update scenes at least to POV-Ray 3.5 syntax if you plan to use them in future versions of POV-Ray.</p>	+	<p class="Warning"><strong>Warning:</strong> The version directive and command-line setting no longer provide compatibility with most rendering bugs in versions prior to POV-Ray 3.5. However, compatibility with the scene language is provided for scenes as old as POV-Ray 1.0 just as in all previous versions of POV-Ray. Nevertheless, we strongly recommend you update scenes at least to POV-Ray 3.7 syntax if you plan to use them in future versions of POV-Ray.</p>

@@ Line 3: / Line 3: @@
 {{#indexentry:#version}}
 {{#indexentry:version}}
-<p>As POV-Ray has evolved from version 1.0 through 3.7 we have made every effort to maintain some amount of backwards compatibility with earlier versions. Some old or obsolete features can be handled directly without any special consideration by the user. Some old or obsolete features can no longer be handled at all. However <em>some</em> old features can still be
+<p>As POV-Ray has evolved from version 1.0 through 3.8 we have made every effort to maintain some amount of backwards compatibility with earlier versions. Some old or obsolete features can be handled directly without any special consideration by the user. Some old or obsolete features can no longer be handled at all. However <em>some</em> old features can still be
 used if you warn POV-Ray that this is an older scene. The <code>#version</code> directive can be used to switch version compatibility to different setting several times throughout a scene file. The syntax is:</p>
 <pre>

@@ Line 26: / Line 26: @@
 <code>#version</code> directive appearing, the version defaults to 3.62. Additionally, if the first <code>#version</code>
 appears after any other declaration, or a <code>#version</code> directive does not appear at all,
-a post-parse warning is issued, and a {{Change}} as of POV-Ray 3.7.1 or later it is now considered an outright error to use
+a post-parse warning is issued, and a {{Change}} as of POV-Ray 3.8 or later it is now considered an outright error to use
-<code>#version 3.71</code> or higher in a main scene file that does not start with a <code>#version</code> directive.</p>
+<code>#version 3.8</code> or higher in a main scene file that does not start with a <code>#version</code> directive.</p>
 <p>If you do need to do some processing before you decide on a version compatibility option, start your scene with the following
@@ Line 36: / Line 36: @@
 Note that unless the version compatibility option has explicitly been set by the INI file option <code>Version=</code><em>n.n</em>
 or by the <code>+MV</code><em>n.n</em> command-line switch, <code>version</code> evaluates to the actual POV-Ray software version
-when used inside the first <code>#version</code> statement, even in version 3.7.1 or later where it evaluates to the effective
+when used inside the first <code>#version</code> statement, even in version 3.8 or later where it evaluates to the effective
 version compatibility option anywhere else.
 <p class="Warning"><strong>Warning:</strong> The version directive and command-line setting no longer provide compatibility with most rendering bugs in versions prior to POV-Ray 3.5. However, compatibility with the scene language is provided for scenes as old as POV-Ray 1.0 just as in all previous versions of POV-Ray. Nevertheless, we strongly recommend you update scenes at least to POV-Ray 3.5 syntax if you plan to use them in future versions of POV-Ray.</p>

@@ Line 1: / Line 1: @@
 [[Category:Language Directives]]
 {{#indexentry:Directives, language, #version}}
-{{#indexentry:#version|version}}
+{{#indexentry:#version}}
 <p>As POV-Ray has evolved from version 1.0 through 3.7 we have made every effort to maintain some amount of backwards compatibility with earlier versions. Some old or obsolete features can be handled directly without any special consideration by the user. Some old or obsolete features can no longer be handled at all. However <em>some</em> old features can still be
 used if you warn POV-Ray that this is an older scene. The <code>#version</code> directive can be used to switch version compatibility to different setting several times throughout a scene file. The syntax is:</p>