In article <Xns### [at] netplexaussieorg>,
ingo <ing### [at] tagpovrayorg> wrote:
> What if POV-Ray internally expands the mesh2? If it does, that would take > some parsing time.
The mesh2 syntax is closer to the internal format. It doesn't get
"expanded" to anything.
--
Christopher James Huff <cja### [at] earthlinknet>
http://home.earthlink.net/~cjameshuff/
POV-Ray TAG: chr### [at] tagpovrayorg
http://tag.povray.org/
In article <Xns### [at] netplexaussieorg>,
ingo <ing### [at] tagpovrayorg> wrote:
> To an unoptimised mesh?
And for what possible reason would it do that? You're talking about
adding yet another data structure for storing meshes, with the only
result being more work to read a mesh.
--
Christopher James Huff <cja### [at] earthlinknet>
http://home.earthlink.net/~cjameshuff/
POV-Ray TAG: chr### [at] tagpovrayorg
http://tag.povray.org/
in news:cja### [at] netplexaussieorg Christopher
James Huff wrote:
>> To an unoptimised mesh?> > And for what possible reason would it do that?
I awnsered to Warp what to me seemed a possibillity, but since I know
nothing about the internals of POV-Ray, as you know, I added a
questionmark. I answered Warp befor I saw your awnser.
> You're talking about > adding yet another data structure for storing meshes, with the only > result being more work to read a mesh.
I'm not talking about adding anything.
Ingo
aussie