Hi!
8-Мар-2004 14:57 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to
[EMAIL PROTECTED]:
>> And this will be another mistake: in C/C++ standard `char' may be
>> signed, and _it is_ (by default) in BC. (But not in OW, BTW). Stupid, but
>> this is so.
>> This (troubles with sign extension) is why I suggest, that machine
>> specific types NEVER SHOULD BE SIGNED (as they are in FD kernel).
LG> It's easy to just add a -K option to turboc.cfg to force unsigned char.
Unfortunately, this may (and will) add some troubles for BC. For
example, with this options will not compiled C++ programs, which uses
iostream.h.
LG> But this may lead to some code increase and possible side effects...
Again: some (small!) code reducing doesn't justice opened holes (which
_very_ often produces buggy code).
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click
_______________________________________________
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel
