Message172427
| Author |
christian.heimes |
| Recipients |
christian.heimes, ned.deily, pitrou, serhiy.storchaka |
| Date |
2012年10月09日.00:45:48 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1349743549.57.0.654530295366.issue16166@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
My proposal mimics the API of endian.h. It defines a BYTE_ORDER macro that is either equal to LITTLE_ENDIAN, BIG_ENDIAN or PDB_ENDIAN (aka mixed endian). I need it that way for Keccak but I can roll my own definitions if you prefer just two macros.
If you prefer two macros instead of three then we should name them PY_IS_LITTLE_ENDIAN and PY_IS_BIG_ENDIAN.
Ned:
If I understand you correctly than we can't have a configure definition and need macro magic like brg_endian.h. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年10月09日 00:45:49 | christian.heimes | set | recipients:
+ christian.heimes, pitrou, ned.deily, serhiy.storchaka |
| 2012年10月09日 00:45:49 | christian.heimes | set | messageid: <1349743549.57.0.654530295366.issue16166@psf.upfronthosting.co.za> |
| 2012年10月09日 00:45:49 | christian.heimes | link | issue16166 messages |
| 2012年10月09日 00:45:48 | christian.heimes | create |
|