On Sat, 17 Nov 2001 04:02, Craig R. McClanahan wrote: > On Fri, 16 Nov 2001, Jeff Turner wrote: > > Java's official versioning spec [1] seems curiously irrelevant. It talks > > about API specifications, and implementations thereof; not the sort of > > scenario most people deal with. It's primary use-case seems to be > > applets (it amuses me how Sun documents can be dated this way;) > > I'm not so sure this concept is irrelevant to general purpose application > development. > > * Does your application architecture expose abstractions as > interfaces (or abstract classes)? > > * Do you have more than one implementation of those abstractions? > > * Do the implementations rev independently of (and probably at a faster > rate than) the abstractions? > > If so, exactly the same versioning model is quite reasonable.
except of course that the spec offers no method to indicate that your specification is backwards incompatible with previous versions. That alon makes it almost irrelevent. -- Cheers, Pete ---------------------------------------------------------------- Fools ignore complexity. Pragmatists suffer it. Some can avoid it. Geniuses remove it. -- Perlis's Programming Proverb #58, SIGPLAN Notices, Sept. 1982 ---------------------------------------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
