POV-Ray : Newsgroups : povray.general : #version directive : Re: #version directive Server Time
25 Apr 2024 17:52:42 EDT (-0400)
  Re: #version directive  
From: clipka
Date: 7 Feb 2018 15:55:50
Message: <5a7b67d6$1@news.povray.org>
Am 07.02.2018 um 21:48 schrieb Stephen:
> On 07/02/2018 20:03, Mike Horvath wrote:
>> On 2/7/2018 7:13 AM, Stephen wrote:
>>> Parse Warning: This scene had other declarations preceding the first
>>> #version directive. Please be aware that as of Pov-Ray 3.7, un1ess
>>> a1ready specified via an INI option, a #version is expected as the
>>> first declaration in a scene file. If this is not done, POV—Ray may
>>> apply compatibility settings to some features that are intended to
>>> make pre - 3.7 scenes render as designed. You are strongly encouraged
>>> to add a #version statement to the scene to make your intent c1ear.
>>> Future versions of Pov-Ray may make the presence of a #ver51on
>>> mandatory.
>>>
>>> Which means it might not work in the future.
>>>
>>
>> Yes, that's what I was worried about.
>>
> 
> Me too as I use a modeller and the version correction is done after the
> global settings.

As long as the `#version` statement specifies a value of 3.7 or lower,
this will continue to work even in future versions.


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.