On Thu, Dec 31, 2015 at 6:21 AM, John M <john.wilkinson...@gmail.com> wrote:
> > Is the approach of adding new API and deprecate the old sound acceptable? > Or are public API changes acceptable? > I'd vote for the first approach - add new API, but mark the old one as deprecated. At one point the deprecated API should be removed (maybe on a minor version change?) so as to prevent a lot of cruft gathering in the library As to Egons concern regarding maintenance burden - I think it's a safe to state that deprecated API's will not be maintained. -- Rajarshi Guha | http://blog.rguha.net NIH Center for Advancing Translational Science
------------------------------------------------------------------------------
_______________________________________________ Cdk-user mailing list Cdk-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cdk-user
