On 2014-12-04 08:05, Baltissen, GJPAA (Ruud) wrote: > Spiro wrote: >> Unfortunately, as soon as you use .org in ca65, ... > > I'm not familiar enough with CA65 to understand what this means. My > guess: using .org probably means you cannot reallocate BINs? Then my > question: is that a problem for generating these particular BINs? This is one of the most powerful, yet probably most misunderstood feature of ca65 (cc65 as a whole) - it let's one write programs for the 6502 in a more abstract way than we got used to during CBMs heyday. It generates fully relocatable code by default. No need to think much about how to code stuff so that it ends up in a proper place. The compiled / assembled code is then linked and only upon linking, all the object segments fall into their appropriate places. When understood correctly (somewhat tricky at first, mostly due to somewhat unintuitive configuration) this becomes a powerful tool that one doesn't want to become deprived of ;-) And a one that distinguishes the cc65/ca65 from more "classic" assemblers. > Anyway, if someone wants to use the sources for his own purposes and > .org doesn't suit him, he can replace them by more suitable > directives. Having said all the above - for a project which is anyway "stoned" in both its size and memory location for good, I don't see anything wrong in using the .org directive. My guess is that these are the cases, for which the directive is available in the first place. -- SD! Message was sent through the cbm-hackers mailing listReceived on 2014-12-05 00:00:44
Archive generated by hypermail 2.2.0.