Calling C Function Pointers from Python

[Neil Hodgson]

> Couldn't the call_foreign_function be internally wrapped in a
> best-try attempt at handling any resulting errors more
> gracefully than with a crash?  E.g., on Win/NT, a SEH
> __try/__except; on Unix, a local attempt to handle any and
> all 'signal's resulting from wild pointers, etc.  No 100%
> safety by any means, of course, but maybe still better...?

   Yes, that is a good feature to add but I don't think it will satisfy the
view that Python should be safe from any such problems. This appears to be
the view of the BDFL.

   Neil