Congratulations to the Python 2.5a1 release! I started adjusting Boost.Python
to work with this new release and it is going very well. I noticed this #define
in pyport.h:
#define PY_SSIZE_T_MAX ((Py_ssize_t)(((size_t)-1)>>1))
However, I couldn't find a corresponding PY_SSIZE_T_MIN which would come in
handy to adjust old code using INT_MIN (from limits.h). Are there arguments
against defining PY_SSIZE_T_MIN? Or is this just an oversight?
Objects/longobject.c uses:
return -PY_SSIZE_T_MAX-1;
To maximize consistency this would seem ideal to me:
pyport.h:
#define PY_SSIZE_T_MIN (-PY_SSIZE_T_MAX-1)
longobject.c:
return PY_SSIZE_T_MIN;
Cheers,
Ralf
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
