If you want an example, fine, but the specifics aren't as important as the approach. One example of classes that are either removed or intended to be removed are the file repositories that Peter Donald (surname to qualify the overloaded reference) asked James to pull into our module because they weren't (and wouldn't be) supported by Avalon. As an instance, it is no big deal. We're happy to support them. As a philosophy, it points to caution that you had better be prepared to support things before you make them part of your release.
Noel,
policywise, these classes (in cornerstone) are unreleased alpha code. So the example is flawed (then again, almost all examples are contrived by definition ;).
cheers,
- Leo
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
