On Wed, Sep 21, 2011 at 8:12 PM, Ingo Koch <ingo.k...@gmx.de> wrote: > Please keep in mind that such an API should not only help implementing > language > bindings for fossil but should also support tool makers. >
We're all agreed on the many potential benefits, i think. The only hurdle is the size of the task. It would be a major overhaul. That's not to discount the idea - i'm all for it. i did in fact start to do this way back in 2008, but quickly found that fossil's use of exit() as an error handling strategy (which makes sense in a standalone app) was just the first of several big worms i'd have to deal with. An other thing: > Seeing how much fossil developer related traffic currently is on the > mailing > list, maybe it is time to setup a new fossil-deve...@lists.fossil-scm.org? > Richard suggested that last week, but i don't think he's gotten around to it yet. For the sake of the non-dev users, who are certainly sick of my chatter by now, i hope he (or someone else with admin access? Bueler?) finds some time for it. -- ----- stephan beal http://wanderinghorse.net/home/stephan/
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
