flossy_cake
14th June 2026, 12:43
global bwdif = BWDIF()
I know you're not supposed to do this because the parser finds it ambiguous whether bwdif points to the global clip or the function.
But in practice I've not had any issues because everything downstream from the above code always references the global clip.
And I know this because if I put
global bwdif = BWDIF().Text("yep definitely the global clip")
It always shows the text when I reference bwdif downstream, even when it's highly convoluted and inside a ScriptClip.
I've asked AI about it extensively but can't get a definitive answer, was hoping someone with more knowledge could comment.
Did this name resolution ambiguity get patched in Avisynth+ at some point in development? Because I could see how adding the brackets at the end of BWDIF() could inform the parser it's a function rather than a variable.
:thanks:
I know you're not supposed to do this because the parser finds it ambiguous whether bwdif points to the global clip or the function.
But in practice I've not had any issues because everything downstream from the above code always references the global clip.
And I know this because if I put
global bwdif = BWDIF().Text("yep definitely the global clip")
It always shows the text when I reference bwdif downstream, even when it's highly convoluted and inside a ScriptClip.
I've asked AI about it extensively but can't get a definitive answer, was hoping someone with more knowledge could comment.
Did this name resolution ambiguity get patched in Avisynth+ at some point in development? Because I could see how adding the brackets at the end of BWDIF() could inform the parser it's a function rather than a variable.
:thanks: