This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | aurel32 |
|---|---|
| Recipients | aurel32, doko, loewis, tim.peters |
| Date | 2008年07月22日.09:04:07 |
| SpamBayes Score | 9.617842e-05 |
| Marked as misclassified | No |
| Message-id | <1216717448.7.0.41011111107.issue1762561@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
AFAIK, this "mixed-endian" format is only used on little endian ARM (old-ABI only). That is true that IEEE 754 does not specify any format. I used the big and little endian code as a template to add the "ARM format", hence IEEE in the name. "mixed-endian" is the term usually used to describe this format in the ARM community. I am not opposed to any other name. OTOH, if you consider that IEEE does not specify any format, "IEEE, little-endian" and "IEEE, big-endian" are also not correct. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年07月22日 09:04:09 | aurel32 | set | spambayes_score: 9.61784e-05 -> 9.617842e-05 recipients: + aurel32, tim.peters, loewis, doko |
| 2008年07月22日 09:04:08 | aurel32 | set | spambayes_score: 9.61784e-05 -> 9.61784e-05 messageid: <1216717448.7.0.41011111107.issue1762561@psf.upfronthosting.co.za> |
| 2008年07月22日 09:04:07 | aurel32 | link | issue1762561 messages |
| 2008年07月22日 09:04:07 | aurel32 | create | |