POV-Ray : Newsgroups : povray.beta-test : \scenes - parsing errors Server Time
1 Nov 2024 15:25:17 EDT (-0400)
  \scenes - parsing errors (Message 1 to 2 of 2)  
From: Gelu Stoicescu
Subject: \scenes - parsing errors
Date: 17 Apr 2002 13:30:15
Message: <3cbdb127$1@news.povray.org>
If you want everything perfect for the big opening, you might want to know
that
\scenes\textures\patterns\crackle2.pov
\scenes\textures\patterns\crackle3.pov
give parsing error (function redefinition in a loop). Adding an #undef
solves everything. Nothing to do with my system, I guess.
The good news is all other scenes in "scenes" and "insert menu" are A-OK (I
checked that the tedious way)

Gelu Stoicescu


Post a reply to this message

From: Christoph Hormann
Subject: Re: \scenes - parsing errors
Date: 17 Apr 2002 14:03:30
Message: <3CBDB8F2.C8F40520@gmx.de>
Gelu Stoicescu wrote:
> 
> If you want everything perfect for the big opening, you might want to know
> that
> \scenes\textures\patterns\crackle2.pov
> \scenes\textures\patterns\crackle3.pov
> give parsing error (function redefinition in a loop). Adding an #undef
> solves everything. Nothing to do with my system, I guess.

No, i had a look and it's caused by the faulty scenes.  Changing the
function #declare to #local is probably the more elegant way.

Rune: I will try to get rid of the max_gradient warnings, will send you
the modified scenes then.

> The good news is all other scenes in "scenes" and "insert menu" are A-OK (I
> checked that the tedious way)

Thanks for confirming this.

Christoph

-- 
POV-Ray tutorials, IsoWood include,                 
TransSkin and more: http://www.tu-bs.de/~y0013390/  
Last updated 16 Apr. 2002 _____./\/^>_*_<^\/\.______


Post a reply to this message

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