Opened 21 months ago
Closed 7 months ago
#10376 closed enhancement (fixed)
Consider replacing long / unsigned long data types?
| Reported by: | SuRGeoNix | Owned by: | |
|---|---|---|---|
| Priority: | wish | Component: | undetermined |
| Version: | unspecified | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Reproduced by developer: | no | |
| Analyzed by developer: | no |
Description
Those data types are platform specific (eg 8-byte in Mac, 4-byte in Win and 4-byte in x86 Linux but 8-byte in x64 Linux) and can cause issues when used from higher libraries (eg. see https://github.com/Ruslan-B/FFmpeg.AutoGen/issues/217) with struct size/alignments.
They shouldn't be many (at least for public API) but the most important one, is the 'unsigned long checksum' in AVIOContext.
(Just wondering, any actual reason of their existence?)
Change History (2)
comment:1 by , 7 months ago
comment:2 by , 7 months ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Closing this as it can be resolved by CLong / CULong types