When including "woods.inc" without any other include files, I get an error
at the end of "woodmaps.inc": "Expected 'color', undeclared identifyer
'Clear' found instead.

Changing both instances of "Clear" on line 471 of woodmaps.inc to "rgbt 1"
makes it work fine. (though that might be messing up the color map.)

Sample scene:

#include "woods.inc"

any confirmation?

- Slime
[ http://www.slimeland.com/ ]
[ http://www.slimeland.com/images/ ]

Post a reply to this message

"Slime" <noo### [at] hotmailcom> schrieb im Newsbeitrag
news:3cc8d10e$1@news.povray.org...
> When including "woods.inc" without any other include files, I get an error
> at the end of "woodmaps.inc": "Expected 'color', undeclared identifyer
> 'Clear' found instead.

Just like for most of the other include files you have to incliude
"colors.inc".

    Thorsten

Post a reply to this message

Thorsten Froehlich <tho### [at] trfde> wrote:
> Just like for most of the other include files you have to incliude
> "colors.inc".

  This is one thing I have always disagreed with (and I have to always
fix this by myself).
  A library should always be usable just as it is (ie. just by including it
and period). If the library depends on another library, it should include it
internally.
  It's extremely user-unfriendly and illogical that the user must know which
libraries depend on which other libraries and in which order he should include
them in order to make them work.

  If you are worried about parsing speed, just enclose the #include statement
in a proper #ifdef block (the one that is defined inside colors.inc).

  Fixing this is good for everyone. Users don't have to struggle with this
problem and the team has one question less to answer.

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message

Warp wrote:
>   This is one thing I have always disagreed with (and I have to always
> fix this by myself).
>   A library should always be usable just as it is (ie. just by
>   including it
> and period). If the library depends on another library, it should
> include it internally.
>   It's extremely user-unfriendly and illogical that the user must know
>   which
> libraries depend on which other libraries and in which order he should
> include them in order to make them work.

I agree.

>   If you are worried about parsing speed, just enclose the #include
>   statement
> in a proper #ifdef block (the one that is defined inside colors.inc).

That won't work. POV-Ray has to read the whole include file because the 
#endif could be in the include file (it's not like C++).

Btw, could you correct your line length to 72? The quoted text isn't 
very well readable.

-- 
Felix Wiemann

Post a reply to this message

> Just like for most of the other include files you have to incliude
> "colors.inc".

This seems rather silly, when the only reason it includes colors.inc is to
use "Clear" twice. There's no reason this couldn't be replaced by rgbf 1.

Anders

--
light_source{6#local D=#macro B(E)#macro A(D)#declare E=(E-#declare
C=mod(E D);C)/D;C#end#while(E)#if(A(8)=7)#declare D=D+2.8;#else#if(
C>2)}torus{1..2clipped_by{box{-2y}}rotate<1 0C>*90translate<D+1A(2)
*2+1#else}cylinder{0(C-v=1).2translate<D+C*A(2)A(4)#end-2 13>finish
{specular 1}pigment{rgb x}#end#end#end-8;1B(445000298)B(519053970)B
(483402386)B(1445571258)B(77778740)B(541684549)B(42677491)B(70)}

Post a reply to this message

Felix Wiemann <Fel### [at] gmxnet> wrote:
>>   If you are worried about parsing speed, just enclose the #include
>>   statement
>> in a proper #ifdef block (the one that is defined inside colors.inc).

> That won't work. POV-Ray has to read the whole include file because the 
> #endif could be in the include file (it's not like C++).

  Wrong. POV-Ray will not execute the #include command if it's skipping
code. A control structure such as #ifdef must start and end in the same
file - it can't start in one file and end in another.

> Btw, could you correct your line length to 72? The quoted text isn't 
> very well readable.

  My lines are as long as I decide to write them.
  I *want* to have full control of what I write. I *don't* want a program
to modify what I write.

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message

>   I *want* to have full control of what I write. I *don't* want a program
> to modify what I write.

So you are not in favour of using spell-checkers? ;-)

    Thorsten

Post a reply to this message