On Thu, 4 Aug 2011, Rugxulo wrote:

> I'm not sure I agree. There's just too much crappy C code out there.
> Worse is that most people force POSIX and fragile / confusing
> AutoTools on everything. And when code assumes certain-sized ints,
> GCC, etc. etc., you'd almost be better writing your own from scratch.
> (If your "configure" is bigger than your total source code size,
> you've done something wrong!!)

Ugh.  I never use autotools - if I ever need a ./configure, I roll my own.

That said, I do tend to assume a certain size of int, but that's an 
averaging of all the C compilers I've used, i.e., I assume "short" is 16 
and "long" is 32.  (This is true of every compiler I've used except Hitech 
C for CP/M.)

That said, stdint.h ftw?  But older compilers don't have it. :/

> Yes, but "most" (??) people won't complain if you personally don't
> support MBF, at least not initially. BTW, I guess you've seen this:

I would think it's almost never a problem to not use MBF by default.

>> IEEE-754 compatible FPU are part of every Intel CPU since the 486,
>
> Correction, 586.   ;-)

486DX.  The only 486s that lacked them were those in the SX line.

> I don't understand how supporting less old code and compatibility is
> seen as an advantage. Companies these days will literally rip out
> functionality and still have the nerve to call it an "upgrade" (and
> charge you for it too, natch). Oh well. I still like the idea of
> emulation / virtualization, though, since it makes (forced, arbitrary,
> annoying) transitions easier.

*nod*

-uso.

------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
The must-attend event for mobile developers. Connect with experts. 
Get tools for creating Super Apps. See the latest technologies.
Sessions, hands-on labs, demos & much more. Register early & save!
http://p.sf.net/sfu/rim-blackberry-1
_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to