[Coco] Need some advice

[Greg]

The issue here is that a lot of the library modules are grouped by 
function type so if you include a call to open, you end up getting 
access, creat, close, dup, open, and unlink. If you reference read or 
write, you automatically get read, readln, write, and writeln. This 
doesn't seem too bad on the surface, but it adds up fairly quickly.

This is one of the reasons I switched to Carl Kreider's library. Carl 
moved most of these routines into their own library modules to 
significantly reduce the overhead, optimized some of the library 
routines, and added a lot of useful new stuff.

On 5/22/2016 1:16:31 AM, "Dave Philipsen" <dave at davebiz.com> wrote:

>Haha!  It's been so long ago I couldn't even remember who it was.  I 
>can't even remember the name of the other comm program I compared 
>against.  And, obviously, at lower baud rates and for just displaying 
>ANSI-encoded text there was probably no perceivable difference between 
>a C program and one written purely in assembler.
>
>I would think another undesirable thing about many C compilers would be 
>that they use libraries which might be included in the final 
>compilation even though some of the code is never used.  That might not 
>be a problem in some cases but when you're writing code for an embedded 
>application with limited memory you don't want to waste anything.  In 
>the past, I've written code for boards that had as little as 2-4K of 
>EPROM space which pretty much would limit you to using assembly.
>
>Dave