[Python-Dev] RE: [Python-checkins] python/dist/src/Python bltinmodule.c,2.276,2.277

[Tim Peters]

[Jack Jansen]
> ...
> If you build with Apple's MPW compilers it probably is, but (a) these
> compilers are horribly outdated and (b) it would take major surgery to
> compile Python with MPW anyway, nowadays.

In that case, can we remove the MPW #ifdef's from the Python core?  Things
like object.c's

#ifdef MPW /* MPW C modf expects pointer to extended as second argument */
{
	extended e;
	fractpart = modf(v, &e);
	intpart = e;
}
#else
	fractpart = modf(v, &intpart);
#endif


and mathmodule.c's flea on the tip of the tail of the dog

#ifdef MPW_3_1 /* This hack is needed for MPW 3.1 but not for 3.2 ... */
FUNC2(pow, power,
      "pow(x,y)\n\nReturn x**y (x to the power of y).")
#else


and acceler.c's germ on the aforemetioned flea's hindquarters:

#ifdef MPW_881_BUG
					/* In 881 mode MPW 3.1 has a code
					   generation bug which seems to
					   set the upper bits; fix this by
					   explicitly masking them off */
					int temp;
#endif


And so on.  These don't really improve maintainability <wink>.