17 Dec
2007
17 Dec
'07
4:20 a.m.
On Dec 16, 2007 12:40 PM, Marc Piulachs <marc.piulachs(a)codexchange.net> wrote:
CONS: baseaddress are still calculated by hand
(but validated
automatically on request).
I don't understand why if it can be validated, it can't be
autogenerated and validated by the same process. It seems like the
validation logic is going to be the same as autogeneration logic so
you might as well have it spit out the address and save having to
write them out by hand in each module, or in the root configuration
for bassaddresses.
--
Steven Edwards
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
As for baseaddress in xml form - baseaddress is a
module's property,
it's not a standalone object which is part of the module. I don't see
why it should be given a standalone tag (maybe I'm missing something).
"property" IS actually an object, which is basically a generic key-value
container. The information it contains is *meaningless* to rbuild as it just
simply returns its value when someone reference it by his key. It can
contain anything from an empty string to Boolean or int ... .Rbuild don't
care about it as there is no way to validate the information they contain
because we don't know what to expect. "baseaddres" by contrast is a
specialized property (the C++ object is actually a property subclass so
technically still a property) which allows us to apply any particular logic
we desire to it , for example , generic property's value can be empty
baseaddres propery's value not. Generic property's value is not required to
be unique but baseaddres property must be. and so on...