search for: stableapi

...unaware for quite awhile. I think this is the most important point, that we lack testing for it. IMO, the language doesn’t matter too much. I’m happy with C or C++, but whichever (or both) or those are exposed in a stable way, we need the *users* of those APIs to help test it. How about we add a StableAPI directory in unittests? Then have a test written in C/C++ for each of the users of it. So a WebKit.c test, Go.c, SomeProject.cpp, etc. Then adding anything to the stable API must have a corresponding test, and changing the API shows us exactly which test broke, who cares about that test, and who...

...> I think this is the most important point, that we lack testing for it. > > IMO, the language doesn’t matter too much. I’m happy with C or C++, but whichever (or both) or those are exposed in a stable way, we need the *users* of those APIs to help test it. > > How about we add a StableAPI directory in unittests? Then have a test written in C/C++ for each of the users of it. So a WebKit.c test, Go.c, SomeProject.cpp, etc. > > Then adding anything to the stable API must have a corresponding test, and changing the API shows us exactly which test broke, who cares about that tes...

On Fri, Jul 17, 2015 at 3:41 PM, Eric Christopher <echristo at gmail.com> wrote: > Hi Juergen, > > I've actually got another, perhaps more radical, plan. Let's just get rid > of the C API or move it to another project. This simplifies a lot of the > plans here where people have too many different ideas of how the C API > should work. > > At this point the