Hi Tim, Regardless of whether a version control system is used, when the person in charge of child class B becomes aware that something has changed in parent class A, we don't require all of those changes to be copied manually from A to B.
That is the situation at the moment with .adl files. When the person in charge of b.adl becomes aware that a.adl has changed, all of those changes have to be copied manually from a.adl to b.adl. - Peter -------------------------------------------------- From: "Tim Cook" <[email protected]> Sent: Thursday, May 08, 2008 6:33 PM To: "For openEHR technical discussions" <openehr-technical at openehr.org> Subject: Re: ARCHETYPE_ONTOLOGY Hi Tom, On Thu, 2008-05-08 at 09:07 +0100, Thomas Beale wrote: > > > sure - it is just like OO code for subclasses - you don't include copies > of the methods and attributes already present in the parent, you only > include those being overridden or added. Doing otherwise creates a > maintenance problem, since child class B, containing copies of class A's > unchanged methods X and Y is out of date as soon as class A is modified > to change or remove X or Y. Correct. In software development you use a version control system to keep everyone up to date. If I change class A, you get a notice and are responsible for making any changes to your child class B. But when we release a complete version of an application we do not send out .diffs for our users to assemble. Cheers, Tim
