RE: [cc65] Modules with self modifying code

Hi,

> From: owner-cc65@musoftware.de [mailto:owner-cc65@musoftware.de] On Behalf
> Of Ullrich von Bassewitz
> Sent: Saturday, February 05, 2011 3:18 AM
> On Sat, Feb 05, 2011 at 01:09:40AM +0100, silverdr@wfmh.org.pl wrote:

> > If my two pennies are of any value then I find
> >
> > >  2. Accept replacement functions using smc, but let them have
> different
> > >     names, so a programmer must explicitly call the smc version.
> >
> > most appealing. Reasons for that:
> 
> In the current situation, I do also see this as the most appealing
> approach:

I like that approach as well, since I think the programmer should have to
choose to use SMC functions, especially on those targets that may be running
code from ROM.

> I'm not sure about the segment question, Oliver brought up. When choosing
> option 2, where a programmer must explitly include and call smc functions,
> I
> would even find it acceptable to place these functions in the CODE
> segment.
> But that doesn't cover target specific functions with smc. We can also use
> another segment like SMCCODE, but the segment list in the config files is
> already quite large and it's difficult for a newcomer to understand the
> purpose of all the segments.

I don't like the idea of another segment for SMC functions... if the
programmer is making the choice to use them, then the programmer is probably
fully aware of the ramifications of the CODE segment having to be in RAM.
 


----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.