This build should fix the issues reported about the tuple-style assignment:

https://github.com/c-lipka/povray/releases/tag/v3.7.1-alpha.8004333

Post a reply to this message

On 03/21/2015 09:58 AM, clipka wrote:
> This build should fix the issues reported about the tuple-style assignment:
>
> https://github.com/c-lipka/povray/releases/tag/v3.7.1-alpha.8004333

some problems building ...

parser/parser.cpp: In member function ‘void 
pov::Parser::Parse_Declare(bool, bool)’:
parser/parser.cpp:8225:18: error: template argument for ‘template<class 
_Tp> class std::allocator’ uses local type 
‘pov::Parser::Parse_Declare(bool, bool)::LValue’
parser/parser.cpp:8225:18: error:   trying to instantiate 
‘template<class _Tp> class std::allocator’
parser/parser.cpp:8225:18: error: template argument 2 is invalid
parser/parser.cpp:8225:27: error: invalid type in declaration before ‘;’ 
token
parser/parser.cpp:8382:17: error: request for member ‘push_back’ in 
‘lvalues’, which is of non-class type ‘int’
parser/parser.cpp:8384:39: error: request for member ‘size’ in 
‘lvalues’, which is of non-class type ‘int’
parser/parser.cpp:8423:45: error: request for member ‘size’ in 
‘lvalues’, which is of non-class type ‘int’
parser/parser.cpp:8424:37: error: request for member ‘size’ in 
‘lvalues’, which is of non-class type ‘int’
parser/parser.cpp:8426:40: error: invalid types ‘int[int]’ for array 
subscript
parser/parser.cpp:8427:33: error: invalid types ‘int[int]’ for array 
subscript
parser/parser.cpp:8428:35: error: invalid types ‘int[int]’ for array 
subscript
parser/parser.cpp:8429:39: error: invalid types ‘int[int]’ for array 
subscript
parser/parser.cpp:8443:37: error: request for member ‘size’ in 
‘lvalues’, which is of non-class type ‘int’
parser/parser.cpp:8445:40: error: invalid types ‘int[int]’ for array 
subscript
parser/parser.cpp:8446:33: error: invalid types ‘int[int]’ for array 
subscript
parser/parser.cpp:8447:35: error: invalid types ‘int[int]’ for array 
subscript
parser/parser.cpp:8448:39: error: invalid types ‘int[int]’ for array 
subscript

Post a reply to this message

Am 28.03.2015 um 13:04 schrieb James Holsenback:
> On 03/21/2015 09:58 AM, clipka wrote:
>> This build should fix the issues reported about the tuple-style
>> assignment:
>>
>> https://github.com/c-lipka/povray/releases/tag/v3.7.1-alpha.8004333
>
> some problems building ...
>
> parser/parser.cpp: In member function ‘void
> pov::Parser::Parse_Declare(bool, bool)’:
> parser/parser.cpp:8225:18: error: template argument for ‘template<class
> _Tp> class std::allocator’ uses local type
> ‘pov::Parser::Parse_Declare(bool, bool)::LValue’

Ah, somehow I had a feeling that might cause problems.
Can you try pulling the definition of "struct LValue" out of the 
function and see whether that fixes all the errors?

Post a reply to this message

On 03/29/2015 09:25 AM, clipka wrote:
> Am 28.03.2015 um 13:04 schrieb James Holsenback:
>> On 03/21/2015 09:58 AM, clipka wrote:
>>> This build should fix the issues reported about the tuple-style
>>> assignment:
>>>
>>> https://github.com/c-lipka/povray/releases/tag/v3.7.1-alpha.8004333
>>
>> some problems building ...
>>
>> parser/parser.cpp: In member function ‘void
>> pov::Parser::Parse_Declare(bool, bool)’:
>> parser/parser.cpp:8225:18: error: template argument for ‘template<class
>> _Tp> class std::allocator’ uses local type
>> ‘pov::Parser::Parse_Declare(bool, bool)::LValue’
>
> Ah, somehow I had a feeling that might cause problems.
> Can you try pulling the definition of "struct LValue" out of the
> function and see whether that fixes all the errors?
>

Well it was much more involved than that ... after commenting out the 
struct LValue definition it started belching on lvalves. I found the 
appropriate set up for that in the previous version (alpha.7981337) file.

Attached is the ~source/parser/parser.ccp file that ended up compiled 
successfully.

Post a reply to this message

Attachments:
Download 'us-ascii' (300 KB)

Am 29.03.2015 um 18:16 schrieb James Holsenback:

>> Ah, somehow I had a feeling that might cause problems.
>> Can you try pulling the definition of "struct LValue" out of the
>> function and see whether that fixes all the errors?
>
> Well it was much more involved than that ... after commenting out the
> struct LValue definition it started belching on lvalves. I found the
> appropriate set up for that in the previous version (alpha.7981337) file.

Sorry, misunderstanding - what I meant was placing the "struct LValue" 
definition before the function rather than inside it, not removing it 
entirely.

Post a reply to this message

On 03/30/2015 08:51 AM, clipka wrote:
> Am 29.03.2015 um 18:16 schrieb James Holsenback:
>
>>> Ah, somehow I had a feeling that might cause problems.
>>> Can you try pulling the definition of "struct LValue" out of the
>>> function and see whether that fixes all the errors?
>>
>> Well it was much more involved than that ... after commenting out the
>> struct LValue definition it started belching on lvalves. I found the
>> appropriate set up for that in the previous version (alpha.7981337) file.
>
> Sorry, misunderstanding - what I meant was placing the "struct LValue"
> definition before the function rather than inside it, not removing it
> entirely.
>

I pulled struct LValue out of the function and placed it just before the 
function and no joy, so I went up to the top of the file just inside the 
namespace pov specification. In both cases the error was the same:

parser/parser.cpp:8217:9: error: ‘Token_Struct’ does not name a type
parser/parser.cpp: In member function ‘void 
pov::Parser::Parse_Declare(bool, bool)’:
parser/parser.cpp:8378:16: error: ‘struct pov::LValue’ has no member 
named ‘token’
parser/parser.cpp:8426:42: error: ‘struct pov::LValue’ has no member 
named ‘token’
parser/parser.cpp:8445:42: error: ‘struct pov::LValue’ has no member 
named ‘token’

Even though this didn't make sense to do so I then moved it just above 
the namespace pov definition (after the last include) and there was more 
fallout, so I think that confirms my initial assumption that it didn't 
make sense:

parser/parser.cpp:104:9: error: ‘Token_Struct’ does not name a type
parser/parser.cpp:106:9: error: ‘SYM_ENTRY’ does not name a type
parser/parser.cpp: In member function ‘void 
pov::Parser::Parse_Declare(bool, bool)’:
parser/parser.cpp:8378:16: error: ‘struct LValue’ has no member named 
‘token’
parser/parser.cpp:8379:16: error: ‘struct LValue’ has no member named 
‘tempEntry’
parser/parser.cpp:8426:42: error: ‘struct LValue’ has no member named 
‘token’
parser/parser.cpp:8428:37: error: ‘struct LValue’ has no member named 
‘tempEntry’
parser/parser.cpp:8445:42: error: ‘struct LValue’ has no member named 
‘token’
parser/parser.cpp:8447:37: error: ‘struct LValue’ has no member named 
‘tempEntry’

Post a reply to this message

Am 28.03.2015 um 13:04 schrieb James Holsenback:
> On 03/21/2015 09:58 AM, clipka wrote:
>> This build should fix the issues reported about the tuple-style
>> assignment:
>>
>> https://github.com/c-lipka/povray/releases/tag/v3.7.1-alpha.8004333
>
> some problems building ...

Current official master should fix the Unix build issues.

Post a reply to this message

On 03/30/2015 02:18 PM, clipka wrote:
> Am 28.03.2015 um 13:04 schrieb James Holsenback:
>> On 03/21/2015 09:58 AM, clipka wrote:
>>> This build should fix the issues reported about the tuple-style
>>> assignment:
>>>
>>> https://github.com/c-lipka/povray/releases/tag/v3.7.1-alpha.8004333
>>
>> some problems building ...
>
> Current official master should fix the Unix build issues.
>
indeed it does ...
ash@linux-c2bm:~/ScratchPad/povray $ povray --version
POV-Ray 3.7.1-alpha.8017570.unofficial

Post a reply to this message

clipka <ano### [at] anonymousorg> wrote:
> This build should fix the issues reported about the tuple-style assignment:
>
> https://github.com/c-lipka/povray/releases/tag/v3.7.1-alpha.8004333

There still seems to be problems. Please try this:

// POV-Ray: v 3.7.1-alpha.8004333.unofficial.msvc10(?)
// Binary: pvengine64.exe
// OS: Windows 8.1 (64 bits)
// CPU: AMD A8-6410

#declare A = array[3];

/*
#declare A[0] = 1;
#declare A[1] = A[0];

// "Parse Error: Attempted to redefine float identifier as array identifier."
#declare A[2] = array[1] { 1 };

#declare E = A;
*/

// "Unfortunately, it appears that a memory access violation at address
// 0x00007FFBE6F3262B has caused this unofficial POV-Ray build to crash."
#declare (A[0], A[1], A[2], E) = (1, A[0], array[1] { 1 }, A);

--
Tor Olav
http://subcube.com

Post a reply to this message

Am 02.04.2015 um 21:14 schrieb Tor Olav Kristensen:
> clipka <ano### [at] anonymousorg> wrote:
>> This build should fix the issues reported about the tuple-style assignment:
>>
>> https://github.com/c-lipka/povray/releases/tag/v3.7.1-alpha.8004333
>
> There still seems to be problems. Please try this:
>
> // POV-Ray: v 3.7.1-alpha.8004333.unofficial.msvc10(?)
> // Binary: pvengine64.exe
> // OS: Windows 8.1 (64 bits)
> // CPU: AMD A8-6410
>
> #declare A = array[3];
>
> /*
> #declare A[0] = 1;
> #declare A[1] = A[0];
>
> // "Parse Error: Attempted to redefine float identifier as array identifier."
> #declare A[2] = array[1] { 1 };
>
> #declare E = A;
> */
>
> // "Unfortunately, it appears that a memory access violation at address
> // 0x00007FFBE6F3262B has caused this unofficial POV-Ray build to crash."
> #declare (A[0], A[1], A[2], E) = (1, A[0], array[1] { 1 }, A);

*sigh!*

Looks like this whole thing is a deal more complicated than it first 
seemed...

Post a reply to this message