Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2003-April/034486.html below:

[Python-Dev] Re: tp_clear return value

• 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 ]

Tim Peters wrote:
> [martin@v.loewis.de]
> > Beautiful is better than ugly.
> 
> Whish is another reason <wink> it would be nice to get rid of the endlessly
> repeated masses of ugly
> 
> 	if (err)
> 		return err;
> 
> incantations out of the many tp_traverse slots, in return for putting a
> little bit of setjmp/longjmp ugliness in exactly four functions hiding in a
> single module.

I agree that concentrating the ugliness is good.  However, how portable
is setjmp/longjmp?  The manual page I have says C99.  Can we rely on it
being available?  If not, could we just disable the gcmodule functions
that depend on it?

  Neil

• 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 ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4