Re: [Anygui-devel] Possible signaling semantics

[Magnus L. H. <ml...@id...>]

From: "Patrick K. O'Brien" <po...@or...>

> ## signal.py

Hm. This would shadow the standard module signal...

> def send(signal, sender, **kwds):

Any reason why the order is different here from the other two
functions (i.e. why isn't sender first?)

I can see the "send signal" thing, but even so I think it would
be better to be consistent -- especially since it is similar to
the "self" convention...

Anyway, I think send(sender, signal, **kwds) is a good signature
for this function. (Possibly send(source, signal, **kwds)).

Perhaps we should go for send(), connect() and disconnect()?

Or perhaps, send(), listen() and ignore()? Those weren't too bad,
were they? I.e.

  send(source, signal, **kwds)
  listen(source, signal, handler)
  ignore(source, signal, handler)

Hey... listen and ignore even have the same number of letters...
(The same number as signal, even...)

Though it is a bit odd that a handler should listen to
something...

("Why won't he stop!" I hear them shout... <wink>)

> Patrick K. O'Brien

--
Magnus Lie Hetland                       The Anygui Project
http://hetland.org                       http://anygui.sf.net