Re: [cc65] some patches

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> 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,

Ok, of course it does not have to be compiled in by default. I was thinking
about something like this:

#define __USE_IDE64

At the beginning of a the user's program would redefine a few routine calls to
alternative versions in the library header files (stdio.h, unistd.h) for
read/write and possibly seek.

> 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

What is the reason for the final RESTOR? Interrupts are restored already,
anything else?

> 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.

There would be no cost if it's not selected.

> 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
> hazzle.

I'm not sure if this is a good idea, at least I would not do it.

- --
						    -soci-
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkueq+IACgkQyBOVYiJltRZ3AwCg4GtDv20DyL3uwGscPaQsmpaK
VYUAnRhC2WMPjlamLd3lNT4oQrY7oBkw
=QqdI
-----END PGP SIGNATURE-----
----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.