Hmm. Not opposed in principle. I know I don't have to tell you this, but since I've made this mistake so many times myself (sigh) I'm going to suggest that you take the following steps in sequence:
(a) Enable the new way in parallel with the old way, if you haven't already done so. (b) Post (here and on website) a good illustration of old way/new way to simplify code conversion (c) Deprecate the old call, making sure the javadoc is updated to explain why it's deprecated and, preferably, to include or point to the illustration. (d) Give people a release cycle or two to notice and to correct their code before you remove the methods. (Yeah, I know, XNI is experimental and subject to change. But this looks like a case where the impact of the cut-over can be managed fairly painlessly...) ______________________________________ Joe Kesselman / IBM Research --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
