Dale heeft geschreven in bericht <371E63C9.B10CB84D@execpc.com>...
>Partially.  Because of the increasing complexity of  Pov,  it was necessary
>to make the syntax a little more ridged  in delimiting values and
>statements than the earlier versions, to avoid conflicts and bugs.  Needing
>semi-colons after #declares are an example.  <snip>


Great! I am sometimes very puzzled by the anomalies in the POV definition
language. A more rigid syntax design may require more initial typing, but I
am convinced that it strongly reduces the overall TTFR
(Time-To-Final-Render), especially for those users that work as chaotic as I
do.

Some modifications spring to mind:
1 - to require commas between all arguments at all times
2 - make using a texture obligatory  (it may only contain a pigment, ok)
3 - introduce separate #end statements:  for #if blocks (#endif), #while
blocks (#endwhile), #switch (#endswitch) blocks, and so on
4 - semicolons after all #define commands

The parser will become more redundant, easier to expand, probably faster,
etc. Portability with code for previous may pose a problem. We have already
accomodated a 'break' in backward compatibility with version 3, and a more
rigid language design now may prevent more problems later.

Frans Verbaas

                                                Keep in touch with the Dutch
!!!

Post a reply to this message