On Wednesday 27 July 2005 17:42, Paul Davis wrote: > On Wed, 2005-07-27 at 11:25 -0500, Doug Gregor wrote: > > So, here's big question #1: > > > > What the heck do we call a signal? I'd like to call it "signal", but > > that name is already taken in namespace "std". Some other ideas, in no > > particular order: > > > > 1) publisher (and "subscriber", for slots) > > 2) event > > 3) delegate > > 4) multifunction (since there's a "function" already in tr1) > > 5) subject (and "observer", for slots; probably too generic) > > event++ > > i've always disliked the way that the terminology "signals and slots" > hides what is actually happening, and makes it hard for some programmers > to understand what this is all for. personally, i'd love to see "event" > and "callback" or "event_handler" for slots.
The problem with "signal" is that a number of people confused it with Unix/C signals. The problem with "event" is that people may confuse it with X events. Furthermore it is not an "event" in the ordinary sense of something occuring from outside. I would favour "sender", "publisher", "broadcaster" for the signal. For the slot, why not "slot" or "receiver". Chris. _______________________________________________ libsigc-list mailing list libsigc-list@gnome.org http://mail.gnome.org/mailman/listinfo/libsigc-list