From: Ullrich von Bassewitz (uz_at_musoftware.de)
Date: 2003-10-10 16:38:27
On Fri, Oct 10, 2003 at 11:53:02PM +0930, Todd Elliott wrote:
> The disassembly output for GEOS sequential files would be split into two
> source code files; One for the header and one for the main code.
>
> For GEOS VLIR files, the disassembly output would be split into seperate
> source code files for the header, individual VLIR records, etc. So, if a
> GEOS VLIR file had ten VLIR records, I'd like to see ten seperate source
> code files corresponding to each VLIR record, in addition to a source code
> file for the header.
I still don't know what a GEOS VLIR file is, but all this sounds really,
really GEOS specific, and I do usually try not to build too much platform
specific knowledge into a tool. This does not mean that what you want is
impossible - but I would prefer to have a general concept for doing such
things instead of building GEOS and Atari and Apple and NES and <insert your
cool 6502 platform here> specific stuff into the disassembler, because the
latter means that I have to change the disassembler for each supported
platform.
So if we can come up with a general concept that covers file formats (and if
someone explains what VLIR files are), it should be possible to add this to
da65.
> Lastly, I would like for DA65 to have support for GEOS address labels
> (r0..r15, etc.) and GEOS function call labels (SetDevice, OpenDisk, etc.)
> into the disassembled source code output. (No GEOS constant labels should
> be used, though.)
What is wrong with just defining the necessary symbols?
Regards
Uz
--
Ullrich von Bassewitz uz_at_musoftware.de
----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo_at_musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.
This archive was generated by hypermail 2.1.3 : 2003-10-10 16:38:39 CEST