Okay. I can see that point. But, when K&R was written, there was much less variety in hardware implementations and type-sizes. At least, that's my belief. It is, sadly, a bit before my day.
Historically, there was much more variety in hardware implementations and type sizes than today. 16-bit ints were common, as were machines that weren't byte-addressed (e.g. machines addressed by 36-bit word).
The current 64-bit problems are nothing compared to the problems in getting software to work with both 16-bit and 32-bit ints.
IMHO, I think it's not unwise to warn about casting a 64-bit pointer value into a 32-bit value. But, you may be right that this is just because programmers too oft tend to assume "pointers are 32-bits", at least in the last 10 years.
The whole point is that when there is an explicit cast, as opposed to an implicit cast, the compiler should accept that the programmer knows what he is doing. Otherwise, there is no need for explicit casts.
Yup. I hope to take a look at this today.
Great! Thanks.
What's the approximate timeline for bundling and releasing 2004b? (Which I'll then need to get updated in the NetBSD pkgsrc tree)
imap-2004b will be released concurrently with Pine 4.62. I don't think that the Pine release is imminent, barring some newly-discovered critical bug.
-- Mark --
http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum.
