On Monday 27 March 2006 15:09, Bob Ippolito wrote: > I'm going to have to disagree here. Unless there's some technical > reason why an explicit registerSignals is necessary, we should just > let implicit registration happen. Writing less code and more > importantly requiring less explanation is a good thing. > > I don't believe that the time and effort saved by detecting typos or > compelling people to "write documentation" is going to be significant > compared to the time and effort saved by not having to do all that > extra typing. Hell, more typing is more typos anyway... probably a > wash or a net loss in typo-saving.
Let's do a little thought-experiment. (1) I write some javascript code for an object. You use that code. You want to connect to a signal that I never refer to. Why would you want to do that? Thus, a connection to a non-existant signal is pointless. (2) In that same object, I make a "signal" call to a signal that I have never before mentioned. How can you have connected to that signal if I have never mentioned it before? Thus, signalling a non-existant signal is pointless. Unless I can declare a signal BEFORE it is signalled, you cannot connect to it, nor can I signal it. In Pythonic terms, think of signals as variables. Both "connect" and "signal" refer to an already existing signal, just as accessing a variable's value refers to a previously declared (or assigned to) variable. Neither of these should implicitly create the signal. The signal should be created by some other process. -- Jonathan Gardner [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~----------~----~----~----~------~----~------~--~---
