Re: [cc65] [ld65] Overwriting fillval for one segment only?

From: Ullrich von Bassewitz <>
Date: 2012-09-12 08:29:09
Good morning!

On Tue, Sep 11, 2012 at 10:29:14PM +0200, Spiro Trikaliotis wrote:
> you are missing rule #2:
> 2. the end is defined as the last byte before the next segment begins
>    (according to rule #1).
>    If there is no next segment, until the end.
>    That is, filler btes at the end of the segment are part of that
>    segment.

If you interpret this rule so that the contents of a segment can be changed by
assigning an offset to *an other* segment, then I think this rule is highly
unreasonable. Just because I change the offset of CODE2 doesn't mean I want
CODE1 to change.
> Thus, a segment begins with the first byte that is issued for this
> segment (as defined specifically, filler bytes do not count for this
> segment), but it ends with the last byte that is issued before the
> beginning of the next segment. Here, filler bytes *do* count.

Yes, but not filler bytes issued for some other segment. Or did you really
interpret this so?



Ullrich von Bassewitz                        
To unsubscribe from the list send mail to with
the string "unsubscribe cc65" in the body(!) of the mail.
Received on Wed Sep 12 08:29:20 2012

This archive was generated by hypermail 2.1.8 : 2012-09-12 08:29:25 CEST