 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Is there any reason, why parse errors are seen twice:
File 'example.pov' line 10: Parse Error: No matching } in 'pigment', { found
instead
File 'example.pov' line 10: Parse Error: No matching } in 'pigment', { found
instead
Fatal error in parser: Cannot parse input.
Render failed
In this case, there is only one '{' in line 10.
Povray is 3.7 RC3.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 18.07.11 11:13, Timo Poikola wrote:
> Is there any reason, why parse errors are seen twice:
>
> File 'example.pov' line 10: Parse Error: No matching } in 'pigment', { found
> instead
> File 'example.pov' line 10: Parse Error: No matching } in 'pigment', { found
> instead
> Fatal error in parser: Cannot parse input.
> Render failed
>
> In this case, there is only one '{' in line 10.
>
> Povray is 3.7 RC3.
http://www.catb.org/~esr/faqs/smart-questions.html
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Timo Poikola wrote:
> Is there any reason, why parse errors are seen twice:
As Thorsten probably intended to convey, answering this
question requires to see a small code sample that reproduces
the effect.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Christian Froeschlin <chr### [at] chrfr de> wrote:
> Timo Poikola wrote:
>
> > Is there any reason, why parse errors are seen twice:
>
> As Thorsten probably intended to convey, answering this
> question requires to see a small code sample that reproduces
> the effect.
Every now and then, if there is any problem which produce a "parse error",
exactly same error message is printed 2 times. This effect is totally
independent on actual reason of error.
2 examples:
----
File 'a.pov' line 2: Parse Error: Expected 'numeric expression', } found instead
File 'a.pov' line 2: Parse Error: Expected 'numeric expression', } found instead
Fatal error in parser: Cannot parse input.
Render failed
a.pov:
global_settings {assumed_gamma 1.5}
box {<-0.5, -0.5, -0.5>, }
light_source {<4, 5, -5>, rgb <1, 1, 1>}
camera {location <5, 5, -5> look_at <0, 0, 0>}
----
File 'b.pov' line 2: Parse Error: Expected 'object', undeclared identifier 'foo'
found instead
File 'b.pov' line 2: Parse Error: Expected 'object', undeclared identifier 'foo'
found instead
Fatal error in parser: Cannot parse input.
Render failed
b.pov:
global_settings {assumed_gamma 1.5}
object { foo }
light_source {<4, 5, -5>, rgb <1, 1, 1>}
camera {location <5, 5, -5> look_at <0, 0, 0>}
----
Povray: 3.7 RC3
Host computer: 64 bit Debian sid, AMD Phenom X4 9950, 8GB ram
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 07/18/2011 05:00 PM, Timo Poikola wrote:
> 2 examples:
> ----
> File 'a.pov' line 2: Parse Error: Expected 'numeric expression', } found instead
> File 'a.pov' line 2: Parse Error: Expected 'numeric expression', } found instead
> Fatal error in parser: Cannot parse input.
> Render failed
> ----
> File 'b.pov' line 2: Parse Error: Expected 'object', undeclared identifier 'foo'
> found instead
> File 'b.pov' line 2: Parse Error: Expected 'object', undeclared identifier 'foo'
> found instead
> Fatal error in parser: Cannot parse input.
> Render failed
yep ... confirmed both these items
> Povray: 3.7 RC3
> Host computer: 64 bit Debian sid, AMD Phenom X4 9950, 8GB ram
>
>
32 bit OpenSuse ... up to date developers copy
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 07/19/2011 10:46 AM, Jim Holsenback wrote:
> yep ... confirmed both these items
honestly never noticed before but (thud) it's /not/ just picking on the
cases mentioned by the original poster ... try specifying scale like this:
<scale 1,0.5,1>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Jim Holsenback wrote:
> honestly never noticed before but (thud) it's /not/ just picking on the
> cases mentioned by the original poster ... try specifying scale like this:
Ok, I also see it on Window version. Never look at errors there
because they appears in the status bar anyway - and only once ;)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Jim Holsenback wrote:
>
>> honestly never noticed before but (thud) it's /not/ just picking on
>> the cases mentioned by the original poster ... try specifying scale
>> like this:
>
> Ok, I also see it on Window version. Never look at errors there
> because they appears in the status bar anyway - and only once ;)
They probably appears twice, but only one is ever displayed, so you
can't notice.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
