From: Spiro Trikaliotis (ml-cbmhackers_at_trikaliotis.net)
Date: 2005-03-29 15:02:00
Hello André,
* On Tue, Mar 29, 2005 at 01:35:21AM +0200 fachat wrote:
> Please see a draft at http://www.rzuser.uni-heidelberg.de/~fs1/o65/
thank you for your time with preparing this new version.
Some comments from the Magdeburgian Jury ;-):
1. I think "d64copy floppy modules" is not a good name. In fact, these
floppy modules are much more generic. I would like the name "opencbm
floppy modules", as "opencbm" is the name of the cbm4win/cbm4linux
API, and that's where these modules come into play.
2. While I wrote my own parser, I stumbled across the definition of the
relocation tables (2.6.4.). IMHO, it is not always clear which (and
how many) bytes follow after the different formats. @@@SRT
3. 2.6.3) undefined references list and 2.6.5) exported globals list:
I want to discuss if it makes sense to define an maximum name length
here. The parser I just wrote uses an upper limit of 1024 byte; any
name longer than this will not be accepted, although it would be
legal with the o65 file format. Anyway, since this file format most
probably will be used with small machines anyway, I do not think it
makes much sense to allow arbitrary length names, does it?
Regards,
Spiro.
--
Spiro R. Trikaliotis
http://www.trikaliotis.net/
http://cbm4win.sf.net/
Message was sent through the cbm-hackers mailing list
Archive generated by hypermail pre-2.1.8.