.....
>
> POV-Ray's reading capabilities aren't meant to read "ordinary" files. Just
> stuff like this.
>
> "string", <1,1,1>, 321.514, "another_string", 4.2333, <3,6>
>

Why did they limit it? That means I have to go into all the Spline Editor
files I'm using and chop all that unreadable data off myself -- or write a
C program to do it... Which means I'd have been better off using an old DOS
type C program.

If they would have done what seems the simpler programming thing and let the
POV user format how data is read then POV-ray would soon be reading files
from Maya, Lightwave and 3D-max.

Why did they rob us of that power?

If you're going to have file reading - why not go all the way... fseek, user
formatting, etc..

fseek and file positioning and char by char reading would make the whole
file reading and writing operations more powerful.

Post a reply to this message