In message <[EMAIL PROTECTED]> on Wed, 5 Sep 2007 07:20:01 -0700, Nathaniel Smith <[EMAIL PROTECTED]> said:
njs> but presumably the goal is to solve real problems :-). Right. However, there are such things as foreseeable problems as well, as long as we don't go too far into lah-lah-land. njs> The one that comes to my mind is "I want netsync hooks called for njs> my CIA notifier *and* my commit mail notifier". This is pretty njs> easy now, just define a hook that calls the others, but anyway, njs> if we wanted more formal machinery for that, then obviously what njs> it would be was a way to register a list of netsync notifier njs> hooks, which are called in some arbitrary order whenever the njs> relevant event occurred, with return values and errors ignored, njs> and no need for any other fancy stuff. Are you saying that we should make this a special case for the netsync hooks? I've no problem with that per se (actually, it could even be easier to code that directly in Lua), but I'm wondering what to do next time an issue like this comes up. Another special solution? njs> Maybe there are other use cases too that I'm not thinking of, njs> they might have other requirements. Point, which also leads to specific special solutions. (this is a little of a "pick your religion" thingy, just like the bazaar and the cathedral ;-)) Cheers, Richard ----- Please consider sponsoring my work on free software. See http://www.free.lp.se/sponsoring.html for details. -- Richard Levitte [EMAIL PROTECTED] http://richard.levitte.org/ "When I became a man I put away childish things, including the fear of childishness and the desire to be very grown up." -- C.S. Lewis _______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel