[Python-Dev] pthreads question: typedef ??? pthread_t and hacky return statements

Tim Peters tim_one@email.msn.com
Fri, 18 Aug 2000 13:09:05 -0400


[Greg Stein]
> That is a silly approach, Tim. This is exactly what autoconf is for.
> Using run-time logic to figure out something that is compile-time
> is Badness.

Remain -0.  autoconf may work slick as snot on Unix derivatives, but each
new symbol it introduces also serves to make people on other platforms
scratch their heads about what it means and what they're supposed to do with
it in their manual config files.  In this case, the alternative is an
obvious and isolated 1-liner that's transparent on inspection regardless of
the reader's background.  You haven't noted a *downside* to that approach
that I can see, and your technical objection is incorrect:  sizeof is not a
compile-time operation (try it in an #if, but make very sure it does what
you think it does <wink>).