From: Shawn Jefferson (sjefferson_at_sd62.bc.ca)
Date: 2003-04-24 17:35:34
>>> Ullrich von Bassewitz <uz_at_musoftware.de> 04/24/03 12:28AM >>>
>On Wed, Apr 23, 2003 at 03:55:05PM -0700, Shawn Jefferson wrote:
>> What about putting the __heaporg definition in another file, so that anyone who
>wanted to change it could do so pretty easily by just redefining it themselves?
>Ditto with the stack definition in crt0.s. I realize that it isn't much of a
>difference (you could just have your own _heap.s function) but it is a little more
>configurable.
>
>There is nothing that prevents you from supplying your own _heap.s and crt0.s
>file, so the situation is exactly as you want to have it.
I was thinking it would be nice not to have to duplicate any code from these modules, that way you don't have to worry about changes that are made between versions of the library source.
>> While we are on that subject, how about taking the EXEHDR definition for the Atari
>target and putting that in a separate file as well? For that matter, probably
>AUTOSTRT too.
>
>You cannot do that, at least not easily. There are no references into these
>segments, so they won't get linked when in separate files.
I'm not sure what you mean here. Can't I just put this into a separate .s file and link it to my program? (with the appropriate .import defs.)
; EXE header
.segment "EXEHDR"
.word $FFFF
.word __CODE_LOAD__
.word __BSS_LOAD__ - 1
¯
Shawn
----------------------------------------------------------------------
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-04-24 17:40:24 CEST