Re: New draft version of o65 file format

From: Ullrich von Bassewitz (uz_at_musoftware.de)
Date: 2005-03-30 09:33:41

On Tue, Mar 29, 2005 at 09:40:21PM +0200, fachat wrote:
> I think with such a number of CPUs one could deprecate the "65816" header mode bit,
> but define the currently unused header mode bits 4-7 into a 4 bit CPU type flag and
> define the CPU types values, so up to 16 CPU types could be handled.

Why not reserve a full byte for the CPU type and use the existing bits for a
subtype? This would in some way extend the current scheme, because the CPU
type would be "65XX" and the subtype would be 6502, 65816 or whatever. 

Since the o65 format is mainly used in the open source world, making version
2.0 (or even 1.4) incompatible is a smaller problem than it would be with
closed source: If I change ld65 to generate the new format and the cc65 module
loader to understand the new format, everybody can just recompile/relink the
existing code to upgrade to 2.0. This is probably true for most other users.
There are no existing .o65 binaries without source that must still work after
a change.

Regards


        Uz


-- 
Ullrich von Bassewitz                                  uz@musoftware.de

       Message was sent through the cbm-hackers mailing list

Archive generated by hypermail pre-2.1.8.