Hi again,

On Tue, May 30, 2017 at 12:18 PM, Rugxulo <rugx...@gmail.com> wrote:
> On Mon, May 29, 2017 at 5:17 PM, Andreas K. Foerster <a...@akfoerster.de> 
> wrote:
>>> > Yes, note that I took great pains to avoid stdio completely.
>>> I don't think printf is the main problem here. But for other compilers
>>> (OW or DJGPP), definitely yes. Still, if you don't need it, don't
>>> require it.
>> Well, when you mentioned printf I thought you understood...
>> Actually not using it made the binaries with bcc several kilobytes
>> smaller. It's not, that it wasn't required. I had to write my own
>> function to print integers. And it's still several kilobytes
>> smaller. ;-)
> I don't remember the size difference with Dev86. It was much more
> noticeable with DJGPP and OpenWatcom than with, say, Turbo C. I've
> written my own printf("%ld",blah) replacement, too.

Here's what I had tested:

[ FreeDOS ] G:\TONY>sed -e "/LITE/,$!d" BCCDEV86.OUT
LITE     EXE         3,320  07-23-16 11:09p
PRINTF   EXE         4,332  07-23-16 11:09p
SCANF    EXE         4,868  07-23-16 11:09p
BOTH     EXE         5,880  07-23-16 11:09p

So roughly 2 kb isn't much savings (compared to 8 kb or 28 kb for others).

Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Freedos-devel mailing list

Reply via email to