'HAVE_STDARG_PROTOTYPES' (consider it true, remove false branch)

char**) and return an int even on PC platforms. If not, please fix
PC/utils/makesrc.c ;-P

Work around intrcheck.c's desire to pass 'PyErr_CheckSignals' to
'Py_AddPendingCall' by providing a (static) wrapper function that has the
right number of arguments.

declarations yet, those come later.

('PyObject** x' -> 'PyObject **x')

and a couple of functions that were missed in the previous batches. Not
terribly tested, but very carefully scrutinized, three times.

All these were found by the little findkrc.py that I posted to python-dev,
which means there might be more lurking. Cases such as this:

long
func(a, b)
	long a;
	long b; /* flagword */
{

and other cases where the last ; in the argument list isn't followed by a
newline and an opening curly bracket. Regexps to catch all are welcome, of
course ;)

paths containing ..

MacPython on MacOSX DP4 gets started in the wrong directory. The workaround (ifdeffed by USE_ARGV0_CHDIR) is to do a chdir() to the folder part of our executable name.

use "cvs diff -b" to verify.

New code will see the macros and therefore use the PyXXX_Size()
APIs instead.
By Thomas Wouters.

clean out some other warnings

* case insensitive comparison

* case insensitive

environments.

distutils patches, which I'll leave to the distutils maintainers.

Tip: review the patch like this:

grep "^[\!+-] " <patchfile>

To get a quick and easy way to review the actual changes. Most of the
changes are single-line ones, anyway.

SourceForge doesn't choke on this batch :-)

I'm not entirely sure this is 100% correct. The patch changes an
\index{persistency} to \index{presistence}, and I don't know what \index{}
does. But it seems to do so persi--er, consistently, so I hope it isn't a
problem.

  (patch #100912)

unicodeobject.c(735) :
    error C2143: syntax error : missing ';' before '}'