[Python-Dev] are NULL checks in Objects/abstract.c really needed? (original) (raw)
Raymond Hettinger python@rcn.com
Thu, 13 Mar 2003 14:15:09 -0500
- Previous message: [Python-Dev] are NULL checks in Objects/abstract.c really needed?
- Next message: [Python-Dev] are NULL checks in Objects/abstract.c really needed?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> i had a quick look at Objects/abstract.c in 2.2.2's source. almost > every function there checks whether the objects it's passed are not > NULL. if they are, SystemError exception occurs. since i've never come > across such exception i've commented out those checks.
Unfortunately, this is part of the safety net for poor extension writers, and I'm not sure we can drop it.
Can we get most of the same benefit by using an assert() rather than NULL-->SystemError?
Raymond Hettinger
- Previous message: [Python-Dev] are NULL checks in Objects/abstract.c really needed?
- Next message: [Python-Dev] are NULL checks in Objects/abstract.c really needed?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]