Message107799
| Author | mark.dickinson |
|---|---|
| Recipients | MrJean1, loewis, mark.dickinson |
| Date | 2010-06-14.16:55:05 |
| SpamBayes Score | 0.007705509 |
| Marked as misclassified | No |
| Message-id | <1276534506.66.0.207374384575.issue3163@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
The proposed addition seems reasonable to me, for native packing and unpacking. For standard mode packing and unpacking, I don't see the point; we'd have to pick a standard size, which would almost certainly be either 4 or 8, and so would already be covered by either the 'iI' or the 'qQ' codes. So I'd suggest adding the size_t/ssize_t codes only for native mode, and leaving them unsupported for the standard modes. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2010-06-14 16:55:06 | mark.dickinson | set | recipients: + mark.dickinson, loewis, MrJean1 |
| 2010-06-14 16:55:06 | mark.dickinson | set | messageid: <1276534506.66.0.207374384575.issue3163@psf.upfronthosting.co.za> |
| 2010-06-14 16:55:05 | mark.dickinson | link | issue3163 messages |
| 2010-06-14 16:55:05 | mark.dickinson | create | |