I never thought about how weird it is that “integer” is abbreviated in C but “unsigned” isn’t
-
-
Replying to @pcwalton
The aesthetic of C (modern era, ignore 6-char external name FORTRAN-era linker limitations in old days) prefers full word (unsigned, volatile) where no nice-sounding prefix shorthand (int, const) exists. Cf. Go’s func & JS’s function (after AWK, d’oh!).
1 reply 3 retweets 10 likes -
Replying to @BrendanEich @pcwalton
So uns would not do and unsign does not stand alone w/o int after, is awkward as adjectived verb if followed by int, adding -ed at end adds 2 chars on 6 (in for a penny) so worthwhile on aesthetic grounds.
1 reply 0 retweets 2 likes -
Replying to @BrendanEich
Could have just been “uint” though, like everyone else did
1 reply 0 retweets 1 like -
Replying to @pcwalton
Heh, that came later but the early pref (I used to write C code like this) was `unsigned` (not `unsigned int`). Lots of Unix code had terrible sizeof(int) assumptions as you know. V6 Unix was written for early C where you could assign pointer to int!
2 replies 1 retweet 3 likes
I still write “unsigned” if I can’t count on stdint.h :)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.