It's the C language. While it's claimed to be "portable," it really doesn't address integer size and endianism well enough.
Oddly enough, even FORTRAN did a better job. You could declare a variable to be INTEGER*4 and that would be that, regardless of architecture. Which ports were causing you headaches? --Brett At 04:17 AM 12/21/2004, Pete French wrote: >> I'd really like to see support for the AMD64 architecture become rock solid, >> too, because 64 bit Athlons are starting to sell at great prices. > >Sadly I went back to running i386 on my AMD64's - not because of problems >with FreeBSD, but because of problems with ports. It seems that theres a lot >of code out there assuming sizeof(int) = sizeof(long). Which is a shame (and >also depresses me after living through identical problems with the 16->32 >switch. You might have thought people would heave learnt) > >-pcf. _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
