You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
asar 1.90
function Foo(bar) = BAR
print dec(Foo(42))
This prints 42. While the fix for this is relatively simple (replacing stribegin() with strncmp() in asar_call_user_function()), it would be a breaking change. Similarly:
asar 1.90
function Foo(bar, BAR) = 123
print dec(Foo(1, 2))
This prints error: (Eduplicate_param_name): Duplicated parameter name: bar in creation of function Foo [function Foo(bar,BAR) = 123]. This is an even simpler fix (replacing stricmp() with strcmp() in createuserfunc()), and isn't breaking, but depends on the first issue being fixed.
The text was updated successfully, but these errors were encountered:
The 1.9 case 1 warning, would it after warning fall back to old behaviour? If so, I would also throw a warning in case 2 about how what the user is trying should work but cannot, due to the case 1 bug, and then also fall back to old behaviour: if a user defines function Foo(bar, BAR) = ..., and case 1 is not fixed but only warned over, BAR would be inaccessible.
This prints
42
. While the fix for this is relatively simple (replacingstribegin()
withstrncmp()
inasar_call_user_function()
), it would be a breaking change. Similarly:This prints
error: (Eduplicate_param_name): Duplicated parameter name: bar in creation of function Foo [function Foo(bar,BAR) = 123]
. This is an even simpler fix (replacingstricmp()
withstrcmp()
increateuserfunc()
), and isn't breaking, but depends on the first issue being fixed.The text was updated successfully, but these errors were encountered: