|
 |
Thorsten Froehlich wrote:
> POV-Ray already does what you are suggesting. in general, your suggestions
> are necessary to get any working parser. POV-Ray does not do massive string
> searches, there are much better ways of finding them and they don't require
> a binary file format or something.
Ooh, good.
> No, the reason for the slow parsing of POV-Ray scenes are mostly related to
> memory allocation. Please note that this topic has been discussed for an
> endless time before, just go back far enough in either povray.general or
> povray.programming .
Hmm, it takes 30 seconds to generate one layer of my dome, but each layer has
<300 pieces.
> > Perhaps it is asking too much...
>
> Why this remark?
Parsers are kinda tedious to write, no?
> > Also, perhaps, different variable types. I don't know how many times
> > I've stored integers between 0 and 10 in an array of doubles...
>
> What is wrong with this in POV-Ray, it will store the integers in the array
> just fine? And they should also work just like any other numbers, after
> all, "real" math doesn't really make a difference between 'doubles' and
> 'integers' either (for the functions POV-Ray offers).
Accuracy and calculation speed.
--
David Fontaine <dav### [at] faricy net> ICQ 55354965
Please visit my website: http://davidf.faricy.net/
Post a reply to this message
|
|
