Message134331
Seems like it should use size_t since it deals with memory location/obj size, but Python doesn't have size_t only ssize_t, and ssize_t is signed...
"m.move(2**32, 10, 4) # Should throw a ValueError" <- Won't it wrap around and become 0 once truncated ?
I've attached a patch that I believe fixes the bounds check, though it's still wrong on the types, since it's not portable. |
|
Date |
User |
Action |
Args |
2011-04-24 13:35:21 | zanella | set | recipients:
+ zanella, amaury.forgeotdarc, rmib |
2011-04-24 13:35:21 | zanella | set | messageid: <1303652121.74.0.690750563013.issue11697@psf.upfronthosting.co.za> |
2011-04-24 13:35:19 | zanella | link | issue11697 messages |
2011-04-24 13:35:18 | zanella | create | |
|