Michael McCandless wrote:
Are you saying we can deprecate these classes in 2.9, and all methods whose signature involves one of these classes, without offering the new classes?
No. Folks should be able to recompile w/o deprecation warnings against 2.9, then upgrade to 3.0. Features should not be deprecated until they have a replacement, unless they're being removed forever.
Doug --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
