Front page | perl.perl5.porters |
Postings from June 2012
Dave Mitchell wrote: >Perhaps its time to bite the bullet and give perl a whole new 64-bit-clean >API? For example, an av_fetch64() with IV rather than I32 args. Don't embed "64" in the name if you don't mean it. "av_fetchiv", please. >Providing a completely new API might also give use the opportunity to >clean up other aspects of the API, not just 64-bit issues. Yes, and this sort of change is consistent with how we've approached API extension in the past. >Or perhaps XS code could just have > > #define USE_64BIT_API > >and magically av_fetch has 64-bit args, Messy. I don't like it. >I suspect the hardest bit may be dealing with public structs that have >32-bit members. I suspect that these generally can just change type. If they can't outright change type, we can probably change the type of actual struct member and have the old accessor macro perform type conversion, with a new accessor macro to get at the new type. Again, we've got precedent for changing how things that look like struct members are actually stored, with the macro layer allowing us to maintain a high degree of compatibility. -zeframThread Previous | Thread Next