Message172403
| Author | pitrou |
|---|---|
| Recipients | christian.heimes, pitrou, serhiy.storchaka |
| Date | 2012-10-08.19:02:20 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1349722852.3361.1.camel@localhost.localdomain> |
| In-reply-to | <201210082150.01041.storchaka@gmail.com> |
| Content | |
|---|---|
> > Ouch, sounds confusing. I would rather have PY_LITTLE_ENDIAN defined only > > on little-endian machines and PY_BIG_ENDIAN only on big-endian machines. > > (and PY_BYTE_ORDER isn't necessary) > > Why use two complementary boolean variables for a single boolean value (Python > does not support mixed endian in any case)? Because it's simply more practical than having to remember which one exists :-) > There is WORDS_BIGENDIAN already. A rather unfortunate IMHO. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012-10-08 19:02:21 | pitrou | set | recipients: + pitrou, christian.heimes, serhiy.storchaka |
| 2012-10-08 19:02:21 | pitrou | link | issue16166 messages |
| 2012-10-08 19:02:20 | pitrou | create | |