|
|
Nikodemus Siivola <tsi### [at] cchutfi> wrote:
: True ;) But could the standard include files should be distributed
: separately? This way the standard library could (maybe) be evolve more
: rapidly, instead of being updated per release...
Because it would be more complicated for the users.
They would have to know there are a set of standard include files somewhere
else, they have to find them, they have to download them and they have to
know how to install them. Also the documentation would have to be separate
from the povray main documentation, which causes even more problems (it's not
a good idea to include in the main povray documentation something which doesn't
come with povray).
And besides, a continuously updated set of include files can be a good
thing, but it can also be a bad thing: If some include files are changed,
then lots of existing pov files can become incompatible with them. That is
there will be a lot of versioning problems. There may be pov-files which
work with the library version 3.5a5, but not with versions 3.5a4 nor 3.5a6.
This can be a headache.
--
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}// - Warp -
Post a reply to this message
|
|