On 1/20/07, Giulio Cesare Solaroli <[EMAIL PROTECTED]> wrote: > THANKS Bob!!!!!! > > You are very right. Thank you very much again, as I probably would > have not spot this myself anyhow. I have spent the last three days > learning deeper how MochiKit.Async works, and why my code was > miss-behaving so badly. > > I don't know why, but returning deferred.callback() looked fine to me. > > Is there any reason why a "return this;" statement could not be added > at the end of the current Deferred.callcack implementation?
I don't see any reason it should. I can't think of a real use case where you'd want that, except in the case where you create an already fired Deferred, but there's better ways to do that (e.g. succeed or fail). Is it worth adding a sentence or two to the documentation and a backwards incompatibility? I don't think so. -bob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~----------~----~----~----~------~----~------~--~---
