Re: [cc65] some patches

From: Ullrich von Bassewitz <>
Date: 2010-03-15 21:30:17
On Mon, Mar 15, 2010 at 09:12:50PM +0100, Groepaz wrote:
> > Is it a good idea to create some header file, which would redefine
> > read/write/fread/fwrite when included? (something like #define read(a,b,c)
> > read_ide64(a,b,c) ) But then I have to make a copy from fread/fwrite as
> >  well...
> no, bad idea. much better idea to simply link custom versions of read/write

That's true. But the real problem is the amount of custom hardware that is in
use. It is impossible to support everybodys pet hardware in the standard cc65
libraries. I cannot produce a separate library for each combination of
patches. A library for the C64 without IDE64 routines for smaller size,
another library for the C64 with IDE64 support. Both with and without the
final call to RESTOR. Another one tailored for JiffyDOS, and one with
optimizations for the C64 DTV. All these in additional variants that use self
modifying code for a small speedup. And so forth ...

So we will have to live with the fact that the cc65 do only cover the most
common case. If it is cheap, they can also cover a few less common ones, too.

Maybe a solution would be if someone starts to offer the standard libraries
for the stable versions in a few less used variants outside of the regular
cc65 distribution. If yomeone is interested in IDE64 support, why not offer a
C64 library for download that has the relevant routines replaced? With some
clever scripting, it shouldn't be too difficult to make the patch process more
or less automatic, so it is possible to track cc65 releases without too much



Ullrich von Bassewitz                        
To unsubscribe from the list send mail to with
the string "unsubscribe cc65" in the body(!) of the mail.
Received on Mon Mar 15 21:30:25 2010

This archive was generated by hypermail 2.1.8 : 2010-03-15 21:30:27 CET