POV-Ray : Newsgroups : povray.beta-test : Finish block dispersion handling. v3.8 (and v3.7). : Re: Finish block dispersion handling. v3.8 (and v3.7). Server Time
2 Aug 2021 02:27:13 EDT (-0400)
  Re: Finish block dispersion handling. v3.8 (and v3.7).  
From: Kenneth
Date: 5 Jul 2021 08:30:00
Message: <web.60e2fa31e6d4fedfd98418916e066e29@news.povray.org>
[Windows 10, running a v3.8xx 'experimental' pvengine  that piggybacks on
v3.7.0]

Both of these examples produce fatal errors:

1) Using ONLY dispersion and dispersion_samples in a finish{}block, PLUS an
interior{ior} block:

Possible Parse Error: Unmatched {
....
Parse Error: No matching }, dispersion found instead

[This warning message makes no sense, IMO]

2) Using BOTH ior and dispersion/dispersion_samples in a finish{} block, but NO
interior {} block:

Parse Warning: Index of refraction value should be specified in 'interior{...}'
statement...   Use of this syntax may not be backwards compatible with earlier
versions of POV-Ray.
Possible Parse Error: Unmatched {
....
Parse Error: No matching }, dispersion found instead

[The 'Parse Warning' part of this message seems to indicate that such syntax can
(or could) be used at some point in the past...but it completely fails in 3.8xx
-- which makes the 'backwards-compatible' part of the warning no longer
necessary or even meaningful now. In other words, how can such syntax be used at
all now if it produces a fatal error anyway? ]

----------

I tried the same constructs in v3.7.0, and got the same fatal errors and warning
messages.

If the 'dispersion' feature was newly added in v3.5-- and was apparently usable
in a finish{} block at that point(?)-- at what point in POV-ray's later
development did such syntax start causing *fatal* errors?


Post a reply to this message

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