Reference:Scene Parsing Options - Revision history

Jholsenback: removed redundant and added link

2018-10-01T00:07:35Z

removed redundant and added link

Jholsenback: alignment

2018-02-11T10:54:13Z

alignment

Jholsenback: consistency

2018-02-10T19:34:09Z

consistency

Jholsenback: removed multi-link markup and minor update

2018-02-10T18:35:19Z

removed multi-link markup and minor update

Clipka: Indexentries fix

2016-12-16T15:05:01Z

Indexentries fix

Clipka: indexentry fix

2016-05-03T23:27:16Z

indexentry fix

Jholsenback: removed obsolete content

2014-09-04T11:49:43Z

removed obsolete content

Jholsenback: indexentry tag repair

2014-05-06T22:48:36Z

indexentry tag repair

Jholsenback: 1 revision: underscore link repair

2012-07-17T18:09:32Z

1 revision: underscore link repair

Jholsenback: still testing that theory

2012-07-12T09:14:48Z

still testing that theory

← Older revision		Revision as of 00:07, 1 October 2018
Line 114:		Line 114:
	</table>		</table>

−	<p>~~As POV-Ray has evolved from version 1.0 through to today we have made every~~	+	<p>See also: [[Reference:Version Directive\|Version Directive]]</p>
−	~~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. In the POV-Ray scene~~
−	~~language you can use the <code>#version</code> directive to switch version~~
−	~~compatibility to different settings.~~ See ~~the section~~ [[Reference:Version Directive\|Version Directive]]
−	~~for more details about the language version directive.~~
−	~~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 one feature introduced in 2.0 that was incompatible with~~
−	~~any 1.0 scene files is the parsing of float expressions. Setting <code>~~
−	~~Version=1.0</code> or using <code>+MV1.0</code> turns off expression parsing~~
−	~~as well as many warning messages so that nearly all 1.0 files will still~~
−	~~work. Naturally the default setting for this option is the current version number.</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 41: / Line 41: @@
      ...
+     }
-#end
+  #end
-−
+  }
 </pre>
 ==Include File Name==

← Older revision		Revision as of 19:34, 10 February 2018
Line 131:		Line 131:
	work. Naturally the default setting for this option is the current version number.</p>		work. Naturally the default setting for this option is the current version number.</p>

−	<p class="Warning">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 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 121: / Line 121: @@
 used if you warn POV-Ray that this is an older scene. In the POV-Ray scene
 language you can use the <code>#version</code> directive to switch version
-compatibility to different settings. See section [[Reference:Version Directive|:#version|The #version Directive]]
+compatibility to different settings. See the section [[Reference:Version Directive|Version Directive]]
 for more details about the language version directive.
 Additionally you may use the <code>Version=</code><em>n.n</em> option or the
@@ Line 131: / Line 131: @@
 work. Naturally the default setting for this option is the current version number.</p>
-<p class="Warning">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">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 7: / Line 7: @@
 assumptions it should make while parsing it.</p>
 {{#indexentry:ini files, constant}}
 {{#indexentry:Declare, ini-option}}
 <table width="100%" class="option-list">
 <tr>
@@ Line 62: / Line 62: @@
 scene file. You can for example use this option to always include a specific
 set of default include files used by all your scenes.</p>
 ==Library Paths==
 {{#indexentry:Include Path}}

← Older revision	Revision as of 18:09, 17 July 2012
(No difference)