From: Ullrich von Bassewitz (uz_at_musoftware.de)
Date: 2005-03-30 10:38:41
On Wed, Mar 30, 2005 at 09:59:48AM +0200, Gabor Lenart wrote:
> BTW, another comment. As far as I know, .o65 format allows one text segment,
> right? I would like to use multiple text segment in the future, like
> initalization code should be dropped after executing at startup. Somewhere
> it is useful.
[...]
> Am I crazy, or it is a useful idea? :)
I have to admit that I don't like the idea. As I said before, the beauty of
the o65 format is its simplicity. For me, it is definitively a disadvantage if
Andre would start to pack all sorts of additional features and optional
headers into the format. The cc65 module loader is less than a half KB in
size, and in my eyes, the goal should be to minimize this even further. But
every feature extension needs more code and will therefore increase the size
of the loader.
This does not mean that the idea of multiple segments itself is bad. cc65
supports many segments and is doing exactly what you describe above (an INIT
segment that may be dropped after startup). But o65 is not the place to do it
- IMHO.
If a more capable format is really needed, my suggestion would be to create a
different format spec, instead of packing all this into o65. But beware: Such
a more capable format would have competition. Currently o65 is the king of its
niche, because it is simple, well defined and allows the smallest possible
loaders on a 6502 machine. With more features, there's also more choice,
because there are other, established object code formats.
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.