On Thu, Oct 06, 2011 at 04:18:27PM +0100, Jacek Cała wrote: > Is this too much hassle to improve the exec in this matter? As said > @Stephan, I think that this option is much more viable than using any > intermediaries like standard output/error, protocol buffers or JSON > API. What do you think? I could spent a bit of my time and look at it > if this is doable and anyone is interested.
Well, it's not that easy, because it plays with fork() and exit(), in order to have simpler code (less cleanup, less heap maintenance, ...) Regards, Lluís > 2011/10/6 Dmitry Chestnykh <dmi...@codingrobots.com>: > > On Oct 6, 2011, at 16:59 , Jacek Cała wrote: > > > >> I've just realized that despite fossil is an executable it does not > >> prevent if from exporting functions for other programs to use (at > >> least on Windows, am not sure if this is possible on *nix). > > > > It doesn't matter how the program is linked. Fossil calls exit() when a > > function needs to fail, and it leaves it up to the OS to clean up allocated > > memory. > > > > -- > > Dmitry Chestnykh > > > > _______________________________________________ > > fossil-users mailing list > > fossil-users@lists.fossil-scm.org > > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
