Perhaps a naive question, but I want to make sure I understand this:

Does the simple use of #undef to un-define something cause any internal problems
in POV-Ray if the 'something' doesn't even exist? Or does it all *require* a
surrounding #ifdef block?

Post a reply to this message

Am 16.05.2013 09:50, schrieb Kenneth:
> Perhaps a naive question, but I want to make sure I understand this:
>
> Does the simple use of #undef to un-define something cause any internal problems
> in POV-Ray if the 'something' doesn't even exist? Or does it all *require* a
> surrounding #ifdef block?

You'll get a parse warning if you try, but if you can live with that 
there's nothing to worry about.

Post a reply to this message

Thanks. Less typing to do. ;-)

I realize my question was an odd one; I'm trying to track down some 'unexpected'
behavior with functions in multiple #include files causing errors in a scene.
("..the function must be #undef first...")  Not a POV-Ray problem-- I found my
mistake.

Post a reply to this message