Bill Janssen wrote:
> So, now I can't build the 3K branch.
>
> This is on OS X 10.5.0, gcc 4.0.1, "make clean; make":
>
> /local/python/3k/src 75 % make
> gcc -o python.exe \
> Modules/python.o \
> libpython3.0.a -ldl
> Undefined symbols:
> "_
> A few hours ago I've renamed the remaining occurrences of PyInt_ to
> PyLong_. Most PyInt_ were aliases for PyLong_ functions. I've also
> removed the inclusion of intobject.h from Python.h but kept the file
> with the aliases for porters from 2.x to 3.0. The remaining functions
> are now in long
> longobject.h has still two PyInt_ functions: PyInt_GetMax and
> PyInt_CheckExact.
>
> long
> PyInt_GetMax(void)
> {
> return LONG_MAX;/* To initialize sys.maxint */
> }
> It's only used for sys.maxint. Do we still need sys.maxint and
> PyInt_GetMax()? IMO PyLong_GetNativeMax() an
A few hours ago I've renamed the remaining occurrences of PyInt_ to
PyLong_. Most PyInt_ were aliases for PyLong_ functions. I've also
removed the inclusion of intobject.h from Python.h but kept the file
with the aliases for porters from 2.x to 3.0. The remaining functions
are now in longobject.h.
On Nov 22, 2007 2:30 AM, Christian Heimes <[EMAIL PROTECTED]> wrote:
> Amaury Forgeot d'Arc wrote:
> > Could this code replace the current PyString_AsStringAndSize, instead
> > of creating a new function?
>
> I guess it could. But it's a naming question. The method is more general
> and takes more
