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 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080508/76c11af1/attachment.asc>
