I'd also point out that the traditional means that API designers use to change an API is to mark existing API they want people to stop using as deprecated, but allow that API to continue to work. Additionally, if I turn on some switch, the API might emit a message saying that some deprecated method is being used.
On Friday, September 7, 2012 8:58:57 AM UTC-7, Stephan Beal wrote: > > On Fri, Sep 7, 2012 at 5:57 PM, mschwartz <[email protected] > <javascript:>>wrote: > >> As I see it, the API you exposed in your header files and documentation >> is something of a contract, and I abided by it. My code has worked >> extremely well and quite robustly for well over a year. You change the >> API, you break my code and expect me to edit tens of thousands of lines of >> C++ code and the deal with the potential instabilities those changes will >> introduce. >> > > Amen, brother. > > As a compromise, may I suggest an alternative to External::New()? How >> about you implement an Opaque::New() that satisfies whatever you feel >> necessary under the hood? >> > > +1 > > -- > ----- stephan beal > http://wanderinghorse.net/home/stephan/ > http://gplus.to/sgbeal > > -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
