[Python-Dev] Re: tp_clear return value (original) (raw)
Tim Peters tim.one@comcast.net
Thu, 10 Apr 2003 18:12:41 -0400
- Previous message: [Python-Dev] Re: tp_clear return value
- Next message: [Python-Dev] Re: tp_clear return value
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[Neil Schemenauer]
I agree that concentrating the ugliness is good. However, how portable is setjmp/longjmp? The manual page I have says C99.
It's also C89, i.e. "ANSI C".
Can we rely on it being available?
I think so. Note that we have three modules that use them now, although they're not compiled everywhere (readline, pcre, fpectl).
If not, could we just disable the gcmodule functions that depend on it?
Jeremy and I have spent a lot of time tracking down leaks (in Python and in Zope) recently, and get_refer{rers, ents} have been invaluable. If we found a platform where {set,long}jmp didn't work, I'd be OK with disabling those two gc functions on that platform. Those functions aren't needed for normal gc operation, and it's not any platform I'm going to be using anyway .
- Previous message: [Python-Dev] Re: tp_clear return value
- Next message: [Python-Dev] Re: tp_clear return value
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]