Null-coalescing transpilation can cause problems in print statements

Consider:

  print "Values:" data.values ?? []

transpiles to:

    print "Values:" (function(data)
            __bsConsequent = data.values
            if __bsConsequent <> invalid then
                return __bsConsequent
            else
                return []
            end if
        end function)(data)

this transpilation causes a run-time error:
Function Call Operator ( ) attempted on non-function. (runtime error &he0)

however, if it is preceded with a semi-colon, then it does not have any problem.

  print "Values:"; data.values ?? []

gives:

   print "Values:"; (function(data)
            __bsConsequent = data.values
            if __bsConsequent <> invalid then
                return __bsConsequent
            else
                return []
            end if
        end function)(data)

If any self-invoking function in transpilation (eg. null-coalescing, ternary, etc.) is in a print statement.. it's probably best to precede it with a semi-colon.

Start by reproducing the issue with the provided BrightScript print statement and inspect the transpilation path for null-coalescing and other self-invoking expressions inside print statements. Done means the example runs without the Function Call Operator runtime error while preserving the intended print behavior, including both separator forms.