INTL 3:770/1 3:770/3
REPLYADDR invalid@invalid.invalid
REPLYTO 3:770/3.0 UUCP
MSGID: 355c7a24
REPLY: 1da6d089
PID: SoupGate-Win32 v1.05
druck writes:
> You can do this on Windows too, but they had to bastardise their C
> compiler for people that hadn't. It's the only one that on a 64 bit
> platform that has long as 32 bits.
>
> Windows:-
>
> int=32 bits, long=32 bits, long long=64 bits
>
> Everyone else in the bloody world:-
(Almost everyone; Cray had 64-bit int.)
> int=32 bits, long=64 bits, long long=64 bits
THe Windows approach is well within what the C language spec allows, and
simplified the adaptation of existing Windows application code to 64-bit
platforms. The equivalent exercise in Linux needed attention to anything
that made (sometimes invisible) assumptions about the definition of
long.
I don’t think I’d fault either decision though the fact that we’ve ended
up with two conventions does make writing/maintaining portable code a
bit more annoying, though not really any more so than the slightly
different set of things compilers warn about or the lack of GCC
compatibility from MSVC. I think MS should bow the inevitable and
replace cl with Clang.
--
https://www.greenend.org.uk/rjk/
--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
SEEN-BY: 10/0 1 90/1 103/705 105/81 106/201 124/5016 129/305 153/757
SEEN-BY: 153/7715 218/0 1 601 700 840 870 930 220/70 221/1 6 360 226/17
SEEN-BY: 226/30 100 227/114 229/110 111 114 200 206 300 317 400 426
SEEN-BY: 229/428 470 550 616 664 700 240/1120 266/512 267/800 282/1038
SEEN-BY: 291/111 292/854 301/1 113 812 310/31 320/219 322/757 335/364
SEEN-BY: 341/66 342/200 396/45 460/58 633/280 712/848 770/1 3 100
SEEN-BY: 770/330 340 772/210 220 230 5020/400 1042 5058/104 5075/35
PATH: 770/3 1 218/840 221/6 301/1 218/700 229/426
|
