POV-Ray : Newsgroups : povray.programming : OBJECT* vs Povray Objects : Re: OBJECT* vs Povray Objects Server Time
3 May 2024 23:32:56 EDT (-0400)
  Re: OBJECT* vs Povray Objects  
From: Le Forgeron
Date: 16 Oct 2007 12:31:32
Message: <4714e764@news.povray.org>
Le 16.10.2007 13:56, Antonio Ferrari nous fit lire :
> Hi,
> I have two questions:
> 
> - 1 - Objects stored into OBJECT struct are the same declared in POV files?
> Suppose you write:
> 
> union {
>   sphere { .......... }
>   sphere { .......... }
> }
> 
> In memory the sphere will be indipendent and referenced by two different
> pointers or in memory I'll find only an OBJECT reference to the union?

I do not know for 3.7 (no source yet), but in previous version, that
code part would have been a CSG objects mother of two spheres
objects (these two being linked in a sibling list).
At each level, you would have found a transformation matrix and a
pointer to the method of the object.
And each object/structure might have additional data

> 
> I expect only one pointer to union, since Parse_Inside receives a generic
> OBJECT*; is it true?

The three objects are presents, and linked. Therefore, the top-level
pointer is enough to keep track of these objects (and therefore the
return of the function...).

> 
> - 2 - Let's suppose we are parsing a density inside a media. When
> Evaluate_TPat is called it receives a pointer to INTERSECTION struct. Is
> there the possibility to have this pointer not NULL for such a kind of
> density? I ask this question because I need that INTERSECTION->OBJECT is a
> pointer to the OBJECT that contains the density that Evaluate_TPat is
> evaluating.


I do not get it. Are you parsing, or rendering ?
in 3.6, only f_pattern (in fnintern.cpp) call Evaluate_TPat with
null as intersection.

-- 
The superior man understands what is right;
the inferior man understands what will sell.
-- Confucius


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.