Earlier quoted context omitted.
It makes sense long would have needed a comment. It needs a comment because “long” and “double” are terrible names for data types. Long what ? Double length what ? Those type names could easily have opposite meanings and meant long floating point / double length integer. WORD/DWORD are nearly as bad - calling something a "word" incorrectly implies the data type has something to do with strings. If you don't believe m…
Yes, int_16/int_32 or something like that makes a lot more sense. Today, not when this compiler was written. The PDP-9, PDP-10, and PDP-18 have 18 bits registers. The world had not settled on 16/32/64 bits at all. Even the intel 80286 far/fat pointers are 24 bits.
Dennis Ritchie’s first C compiler (c. 1972)
161–163 of 163 posts
Re: Dennis Ritchie’s first C compiler (c. 1972)
#162Earlier quoted context omitted.
It makes sense long would have needed a comment. It needs a comment because “long” and “double” are terrible names for data types. Long what ? Double length what ? Those type names could easily have opposite meanings and meant long floating point / double length integer. WORD/DWORD are nearly as bad - calling something a "word" incorrectly implies the data type has something to do with strings. If you don't believe m…
> Microsoft’s WORD/DWORD are nearly as bad. Don’t call something a “word” if it doesn’t store characters. "Word" as a term has been in the wide use since at least 50s-60s, you can't really blame MS for that https://en.wikipedia.org/wiki/Word_(computer_architecture)
You can _absolutely_ blame Microsoft for using it to mean something that it isn't.
Re: Dennis Ritchie’s first C compiler (c. 1972)
#163Earlier quoted context omitted.
What is "guaranteed-ubiquitous" about DOS 3.30?
There are (still!) a lot of copies floating around -- both online and offline -- and it runs on the most pervasive commodity platform that ever existed: 16 bit real mode x86. Those binaries will boot on anything from an ancient IBM PC with an 8088 CPU all the way through to fairly recent x86 systems (if they still have legacy BIOS boot support).
It wouldn't be defensible to use those descriptors for Windows XP. In a word, it would be wrong. Calling DOS 3.30 "guaranteed-ubiquitous" is even wronger than that.