Re: [cc65] - object oriented style

I'm fine with abandoning the idea of being object oriented on this project,
and hard coding a few good LFO's with good old fashioned copy-paste-modify
style programming too :)


There's a whole range of code reuse methodologies in between copy/paste and
OO, you know.  :)  See: functional programming, "good old-fashioned" pre-OO
structured programming, etc.

If the goal is to use abstractions to keep as much as possible
machine-agnostic, then be sure those abstractions are at the right level.
 Consider this:

- non-machine specific LFO routines (low frequency oscillators - based on
> system timers)


That's actually somewhat machine-specific: if you ported your program to the
64/128, you wouldn't need any LFO routines because the SID handles that in
hardware.  In fact, I suspect a good chunk of the functionality you've
written by hand could be delegated to the SID on those systems; looking to
see what you'd have to change to do that might be a good exercise to better
identify some of the places where even your "non-machine specific" code is
insufficiently general because of some assumption or other.

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