POV 3.5 RC6 icl on WinNT Sp 6 PII 233 with 128 MB

following file with following content is parsed fine:

  TEST1.POV:
    #declare A=array[2][2]{ {1,1} {2,2} };

but following files with splitted content returns parse error:

  TEST1.POV:
    #declare A=array[2][2]{ #include "TEST2.INC" };
  TEST2.INC:
    {1,1} {2,2}

Returned from renderer with error status
#declare A=array[2][2]{ # <----ERROR
Parse Error: Missing { after '{', # found instead

When I move '{' and '}' to include file then it not works too.
When I move 'array[2][2]' it works fine.

Documentation states clearly : "The language allows include files to be
specified (...) at any point in the input file."

ABX

Post a reply to this message

Skiba <abx### [at] babilonorg>  wrote:

> Documentation states clearly : "The language allows include files to be
> specified (...) at any point in the input file."

This would also allow:

/*
#include "foo.inc"
*/

You should really not read the documentation as a specification because it
is not and never was meant to be a specification.

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

Skiba <abx### [at] babilonorg>  wrote:

> Documentation states clearly : "The language allows include files to be
> specified (...) at any point in the input file."

This would also allow:

/*
#include "foo.inc"
*/

You should really not read the documentation as a specification because it
is not and never was meant to be a specification.

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

On Fri, 14 Jun 2002 16:02:00 +0200, "Thorsten Froehlich" <tho### [at] trfde>
wrote:
> You should really not read the documentation as a specification because it
> is not and never was meant to be a specification.

I don't. But I want to show points where documentation could be more precise.
Such exception seems strange IMO but if it is intentional design then it is
very easy to find workaround.

ABX

Post a reply to this message