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 | loewis |
|---|---|
| Recipients | doko, loewis, tim.peters |
| Date | 2007年09月04日.03:01:00 |
| SpamBayes Score | 0.073984 |
| Marked as misclassified | No |
| Message-id | <1188874861.21.0.124969015951.issue1762561@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I'm not sure like the naming of the format. "mixed-endian" could mean anything. I doubt IEEE specifies this as a possible byte representation (but then, I'm uncertain whether IEEE specifies big-endian and little-endian, either). One option would be to call it "ARM, mixed-endian", assuming this can be only found on ARM. Another option would be to call it "IEEE, bytes-big-words-little-endian", describing precisely how the format works (IIUC). Tim, any opinion? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2007年09月04日 03:01:01 | loewis | set | spambayes_score: 0.073984 -> 0.073984 recipients: + loewis, tim.peters, doko |
| 2007年09月04日 03:01:01 | loewis | set | spambayes_score: 0.073984 -> 0.073984 messageid: <1188874861.21.0.124969015951.issue1762561@psf.upfronthosting.co.za> |
| 2007年09月04日 03:01:01 | loewis | link | issue1762561 messages |
| 2007年09月04日 03:01:00 | loewis | create | |