Yeah, I saw that too :(
I think we can definitely add a message for None so that this gets
better. At the very least we can report all of the types of arguments
that we received so the None is at least in your face. In general we
want to improve all of our error messages as they're frequently
Hello guys,
I saw a message on Twitter yesterday:
Finding IronPython mildly annoying, with errors like: "TypeError:
Multiple targets could match: AddFile(str), AddFile(FileInfo)"
Needless to say the problem was that he was passing in None - which
could match any of the overloads that take
Alex News wrote:
In the general case this isn't possible:
http://en.wikipedia.org/wiki/Halting_problem
Well it's not strictly a halting problem. The question isn't whether it
will *ever* terminate but just is it taking too long.
IronPython doesn't include this functionality built in but
In the general case this isn't possible:
http://en.wikipedia.org/wiki/Halting_problem
Perhaps some sort of timeout logic would work for you? I.e. kill the
script if it is still running after some predetermined amount of time.
I do not know if IronPython has any such functionality built in, but
i
I have a C# application with IronPython scripting. I wonder, is it possible
to prevent users from creating infinite loops in their scripts?
So for example, if a script is executed which contains a loop, and loop is
infinate, would it be possible for my C# application to detect this, perhaps
by h
