|
 |
:-)
Yes, but then you have no #read problem, maybe just a #write problem and
you will use the great POV parser that will tell you what the problem is.
JC
Warp wrote:
> "JC (Exether)" <no### [at] spam fr> wrote:
>
>>One good way of avoiding any such problem is to write data with the
>>povray syntax, so that you can read it back with a simple #include
>
>
> Well, if you write "<0,0,0)" to an include file and then #include it,
> an error will happen as well, so it isn't really a solution. ;)
>
Post a reply to this message
|
|
|
|
> *SNIP*
>
> Aside of the above, yup, it is nice to simply #include some stuff, but I've
> found in several cases that using the File I/O more like a database rather
> than a crude POV-Editor has some advantages: the code is more compact and,
> though I'm not sure of that, depending on how you use, say, an amount of 500
> Vectors (directly in an array or load them one after another as need) might
> use less memory, but some guru might know more about that (or tell me to
> experiment, which I can't do properly at the moment).
An array of 500 3D vectors takes about 12Kb (8*3*500 bytes), so you are
right but it is mostly in extreme cases when you have enormous amounts
of data and need to fine-tune memory usage that the #include method
couldn't be used.
JC
Post a reply to this message
|
|
