We can have custom versions of some of CC65's library functions.1. They can implement advanced features that haven't been put into CC65's official distribution -- yet.2. Or, they can leave out features that CBM-Command doesn't need. That would reduce the size of the programs.Examples of number 1:"CBM-Command\CBM-Command\cc65*\cputc.s" would use a "folded table look-up" method to convert from PetSCII to screen codes. It is smaller than the current computed conversion method."CBM-Command\CBM-Command\cc65\cbm\clock.s" would use C64/C128 hardware to compensate for the interrupts that the Kernal's datasette and IEC-bus drivers lose.Examples of number 2:"CBM-Command\CBM-Command\cc65\c128\systime.s" wouldn't use the (large) calendar code. CBM-Command doesn't care about the date; only the time-of-day is important."CBM-Command\CBM-Command\cc65\common_printf.s" would leave out the code that implements format-specifiers that CBM-Command won't use (e.g. long, octal, hexadecimal, floating-point, and exotic data-types).