Search
Description
Here is another nasty symbolic bug. Maybe, the custom functions plugin is to blame but I think a bug in the symbolic definition handling is more likely.
This issue emerged in 0.98.5973
0.98.5953 was ok.
Martin Kraska (Wednesday, February 1, 2017 3:42 PM) #
Looks better now, thanks, Davide.
The eval() isn't really required.
Davide (Wednesday, February 1, 2017 1:07 PM) #
Martin, pease try the behavior of undefined arguments with the updated CustomFunctions.