Message172395
| Author | serhiy.storchaka |
|---|---|
| Recipients | christian.heimes, pitrou, serhiy.storchaka |
| Date | 2012-10-08.16:48:31 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1349714911.58.0.736450407844.issue16166@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I agree, it is worth bring order to work with endianess. We can get rod of BYTEORDER_IS_BIG_ENDIAN and BYTEORDER_IS_LITTLE_ENDIAN in Objects/unicodeobject.c, IS_LITTLE_ENDIAN in Objects/longobject.c, tests in other modules. I don't see the necessity in new macros. WORDS_BIGENDIAN is enough. If something failing on a big endian Solaris, build script should just define WORDS_BIGENDIAN. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012-10-08 16:48:31 | serhiy.storchaka | set | recipients: + serhiy.storchaka, pitrou, christian.heimes |
| 2012-10-08 16:48:31 | serhiy.storchaka | set | messageid: <1349714911.58.0.736450407844.issue16166@psf.upfronthosting.co.za> |
| 2012-10-08 16:48:31 | serhiy.storchaka | link | issue16166 messages |
| 2012-10-08 16:48:31 | serhiy.storchaka | create | |