Re: Modifies vs. Replaces

[Michael Eager <eager at eagercon dot com>]

Todd Allen wrote:
> 
> But if the group decides to go with the "augmentation" plan (and Jim's
> "primary" concept in that case, hopefully), then it seems we'd need to
> describe how an "effective location list" is produced by:
> 
>    concatenating the location list from the local copy/copies to the location
>    list from the global (or perhaps in the opposite order, depending on how
>    Jim's primary is determined), and also how a location description is
>    interpreted as a location list with an address range which covers the
>    whole program for this purpose.

I don't think that there are any places where the Dwarf 2 prescribes
a particular implementation.  You seem to be specifying how a consumer
should process location information.

This seems both unnecessary and over specified.  There is existing text
which describes the meaning of location lists with overlapping address
ranges.  I can't see a need for any additional description.

If you are going to claim that people might read the specification 
and do something foolish, you'll have my agreement.  The have in 
the past and most likely will in the future.  We expect that people
reading the Dwarf spec will use it in ways that make good sense,
not ways that seem pointless.  

We seem to be spending an inordinate amount of time on what now
seems to be trivialities of whether to say "modify" or "augment"
or "concatenate".   


-- 
Michael Eager	 Eager Consulting     eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306  650-325-8077