POV-Ray : Newsgroups : povray.pov4.discussion.general : POV SDL Enhancements : POV SDL Enhancements Server Time
29 Nov 2021 22:06:07 EST (-0500)
  POV SDL Enhancements  
From: Theogott
Date: 13 Feb 2016 03:05:03
Message: <web.56bee380b0a91fc8adb2e4f80@news.povray.org>
Here are some point i would like to contribute.

1. Compatibility to the existing scripts and user base is needed.

2. I suggest mixing "old and New".
TO switch from the "Old SDL" to the new SDL, maybe the #version (and a new
#endversion) directive could be used. Using the "#endversion" a second part of
the script could be formulated in the "old" SDL.
I assume that there will be people out there who slowly change their existing
code-base to the new version.
At the end they will just stick with the "Old SDL", if the new one can not be
mixed with the old SDL.

3. I suggest a "Humand readable Frontend" and then a "Machine friendly Backend"
As a multi-Pass system.

4. Possibly a multi-pass system would save work and makes it possible to have
multiple people working on this at the same time.

Seeing that in some (for example "plant growing") scenes, the POV uses still a
lot of time in "reading Tokens", i suggest a Multi-Pass Parsing system with a
human readable front-end and a machine-token (fast to parse) Backend.

A) On Top is a SDL. Theoretically this can be defined by an Editor-PlugIn.
If somebody wants to make an own "specialized SDL" as a Plugin it could be
possible to just "link it into the Editor" and then have a specialized or
enhanced version of the SDL.

B) The second Pass can "expand Macros" until completely expandeded, and
interpret "Compiler Variables".

C) The Output should bow be converted to a definite Standard, could be an
"XML-readable Format" that can also  be generated by Exporters (Blender, etc.)
from 3D-Programs.

D) In the last step this XML should get converted to  Byte-based "Speedcode".
Based on "4 Byte Tokens". These can be parsed in maximum speed by an
"Interpreter". Also the resulting size of the code is very small this way and
fits in CPU/GPU Caches this way. Which is difficult if whole long words are
shifted around as "strings".

As these are multiple Passes, multiple persons can work on it at the same time.
The important point is just that the definitions are "clearly defined".
Once that is done, the rest could be coded in short time.

PS: Error Messages would start like this "Level 4 Error: Memory Limit reached"
or "Level 1 Error: Syntax ERROR expect NEXT for FOR in LINE 4 ".

Post a reply to this message

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