System call conversion for year 2038

Posted May 13, 2015 20:37 UTC (Wed) by eternaleye (guest, #67051)
In reply to: System call conversion for year 2038 by joib
Parent article: System call conversion for year 2038

Oh, ick. 34 bits total of wastage? Sure, struct alignment would mean the same wastage in arrays, but still...

This is really reinforcing my preference for Rust's [ui]{64,32,16,8} integer types over C's (unsigned) {long long,long,int,short,char} fuzzily-sized ones :/

(and Rust then has usize, defined as "capable of holding a pointer", for the cases where that's relevant)

System call conversion for year 2038

Posted May 13, 2015 21:08 UTC (Wed) by rleigh (guest, #14622) [Link] (1 responses)

Are the Rust types not exactly the same as the long established C99 <stdint.h> or C++11 <cstdint>? I haven't used the "fuzzy" types much in over a decade!

System call conversion for year 2038

Posted May 13, 2015 23:01 UTC (Wed) by eternaleye (guest, #67051) [Link]

They are exactly that - but when POSIX defines things in terms of the fuzzy types, even the sensible people who use stdint can't escape.

(of course, for FFI there's libc::c_int and so on, but that's just it: for FFI.)