|
 |
"Kenneth" <kdw### [at] gmail com> wrote:
>
> There IS an obscure built-in identifier (or variable?) called
> View_Include_Stack...
Well... In the light of a new day, I remembered that I had seen that
*somewhere*; it's not an "obscure built-in identifier" :-[ It's just 'a name'
or variable-- part of an #ifdef block at the top of every 'official' POV-ray
include file, with a simple #debug statement:
#ifdef(View_POV_Include_Stack)
#debug "including arrays.inc\n"
#end
It's just a useful/descriptive phrase that someone came up with in the past.
Which explains why adding #declare View_POV_Include_Stack = true; at the
top of your main scene file results in a list of those #included files in
'messages'. Duh. No special magic.
>
> I can't find it in the documentation...
>
...because it's, uh, not part of POV-ray.
>
> Unfortunately, it will not list any user-made #includes-- even if they are
> placed in POV-ray's 'includes' folder; I just tested it. That seems strange.
That's because my personal #include files don't have the added #ifdef block.
Until now, I never gave much thought as to why I should add that. NOW I see why.
It's a good way to see which files might be buried in a large scene with lots of
nested #includes.
I haven't yet tested it to see if it will flag *multiple* instances of the same
#include. That would be useful too.
Post a reply to this message
|
 |