Curt Hagenlocher: This... is... Dynamic!... and StackOverflowException in IronPython
Curt Hagenlocher, the newest (well... as far as I know) member of the IronPython team has started blogging as Iron Curt.
He has two blog entries already. The first explores stack overflow in IronPython (which is a catchable error in Python), and how it maps to the underlying Common Language Runtime (where it is generally an unrecoverable error). By default IronPython doesn't catch stack overflows (sys.recursionlimit is set to MaxInt), because there is a performance overhead in monitoring the frame depth to catch the exception. Curt explores the issues around this for IronPython.
In the second entry he takes this further by looking at CLR exception filters (through the eyes of some VB.NET) to show why they can't be used for IronPython exception handling.
This is part of what it means to be dynamic. Take the power and use it wisely.
He has two blog entries already. The first explores stack overflow in IronPython (which is a catchable error in Python), and how it maps to the underlying Common Language Runtime (where it is generally an unrecoverable error). By default IronPython doesn't catch stack overflows (sys.recursionlimit is set to MaxInt), because there is a performance overhead in monitoring the frame depth to catch the exception. Curt explores the issues around this for IronPython.
In the second entry he takes this further by looking at CLR exception filters (through the eyes of some VB.NET) to show why they can't be used for IronPython exception handling.
This is part of what it means to be dynamic. Take the power and use it wisely.
Comments
Post a Comment