On Sat, Oct 01, 2011 at 09:55:36AM -0400, Richard Hipp wrote: > On Sat, Oct 1, 2011 at 9:07 AM, Paul Ruizendaal <p...@planet.nl> wrote: > > > > > > after every command fossil runs, exit() is called somewhere, which makes > > it difficult or impossible to chain commands together in the same app > > session. > > > > Why? > > > > > I built Fossil using the old-school unix design paradigm of a light-weight > process that does one thing quickly, then exits, leaving the OS clean up the > mess. As long as the process is reasonably light-weight, this pattern works > very, very well. No worries with memory leaks or threads or unwinding the > stack following an error, or any of the other management issues that plague > long-running processes.
I agree with the design. Maybe there is still a way to map that with a stdin/stdout communication, tough. I don't know in detail. As for leaks, the memory leak about annotate was at every checkin traversed, though. Does the change in that branch look fine for a merge? _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
