On 3/26/23 15:32, Bald Eagle wrote:
> After checking that there wasn't some { that got put somewhere by accident, I
> took one of the tuple assignments
> #declare (this, that) = ThisMacroReturns2Values (arg1, arg2, ar3);
> and deleted the trailing semicolon - and BEHOLD!  the error vanishes.
> 
> That makes for coding awkwardness and confusion.
> 
> (I also run into the same kind of thing when I'm putting commas into a cylinder
> {} and use an extra comma in between the second endpoint and the cylinder
> radious - POV-Ray no likey.)

Tried a few things quickly and v3.8 behavior I think OK. Test scene below:

//---
#version 3.8;

#macro Mac00()
     (1,2)
#end

#declare (V1,V2) = Mac00();
#debug concat(str(V1,-1,-1)," ",str(V2,-1,-1),"\n")

#declare (V1,V2) = Mac00()
#debug concat(str(V1,-1,-1)," ",str(V2,-1,-1),"\n")

#declare Cyl00 = cylinder { 0 1 0.1 }
#declare Cyl01 = cylinder { 0, 1 0.1 }
#declare Cyl02 = cylinder { 0, 1, 0.1 }
#declare Cyl03 = cylinder { 0 1, 0.1 }
// #declare Cyl04 = cylinder { 0 1,, 0.1 }  // Valid complaint
// #declare Cyl05 = cylinder { 0 1, 0.1, }  // Valid complaint
// #declare Cyl06 = cylinder { 0, 1,, 0.1 } // Valid complaint

#error "stopping early"
//---

Bill P.

Post a reply to this message