This issue affects my povr branch because in branched off of the updated 
parser. Expect this issue in release which include the parser updates 
(ie not the v3.8 release or earlier).

See: https://github.com/POV-Ray/povray/issues/439

Two examples where the parser should catch the still being defined 
function state and suggest a missing brace as the cause:

// povray +mv3.8 +iScalarFunction_missedBrace.ini
// Missing close brace causing seg fault with v4.0(master) parser updates?
#declare Fn = function {pattern {bozo
}   // <--- Missing close brace }
#declare Vn = Fn(1,2,3);
#debug concat("\nVn = ",str(Vn,1,3),"\n\n")

#error "Parse Test. Stop early"
//---

or

// povray +mv3.8 +iVectorFunction_missedBrace.ini
// Missing close brace causing seg fault with v4.0(master) parser updates?

#declare Fn = function {pigment {bozo
         color_map {[0,rgbft 0][1,rgbft 1]  // <-- missing }
     }}
#declare Vn = Fn(1,2,3);
#debug concat("\nVn = ",vstr(5,Vn,",",1,3),"\n\n")

#error "Parse Test. Stop early"
//---

Bill P.

Post a reply to this message

On 10/3/21 12:23 PM, William F Pokorny wrote:
> This issue affects my povr branch because in branched off of the updated 
> parser. Expect this issue in release which include the parser updates 
> (ie not the v3.8 release or earlier).

Well... Another post proving my mind is glitching. :-(

in branched -> it branched
in release -> in releases
.ini -> .inc

If I start to talk endlessly about turnips, please let me know.

Bill P.

Post a reply to this message