Philip Brown writes: > John Plocher wrote: > > Both are intentionally difficult, because, in general, cross project and > > cross consolidation contracts break the architectural abstractions that > > make it > > possible to maintain our systems. > > > So then it would seem, counter to Richard's original guess, it is by > definition, "incredibly difficult" :-D
It _should_ be hard to trample over architectural barriers. It should probably also be physically painful. ;-} Unfortunately, I don't think what John has said is uniformly true everywhere. There are places where contracts are handed out without substantial thought, and others where the contracts granted are even unenforceable. The interesting cases where these things occur are cases where the interface should have been public in the first place (and, likely, someone is using ARC contracts as a degenerate form of usage tracking) and places where the code isn't necessarily well-maintained. :-/ -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
