Re: [sigc] Proposal for standardization in C++ Library TR2

[Paul Davis <paul linuxaudiosystems com>]

> 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 don't think that events really need to come from outside in most
people's mind. but i do think that the observation about win32
programming and the term "event" is very relevant. its not a good word.

> I would favour "sender", "publisher", "broadcaster" for the signal.  For the 
> slot, why not "slot" or "receiver".

my main object is that this entire mechanism is about using a callback
programming style, something many programmers understand perfectly well.
by using nomenclature like "slot", people don't grasp the basic model.

--p