Re: GSignal documentation

[Tim Janik <timj gtk org>]

On Mon, 20 Aug 2001, Joshua N Pritikin wrote:

> On Sun, Aug 19, 2001 at 11:16:45AM -0400, Havoc Pennington wrote:
> > Joshua N Pritikin <vishnu pobox com> writes: 
> > > Everything is fine, except that the name `instance' is too generic.  It's
> > > really a `scope_instance' -- since everything that connects to a signal's
> > > scope receives emissions.  Contrary to the documentation, i feel like the
> > > signal system doesn't have much to do with objects.  Rather it bridges
> > > scopes and pierces abstraction layers -- i think of it as a run-time
> > > scope system.
> > 
> > What is a "signal's scope"? I don't understand how you are using
> > "scope" here.
> >
> > Signals can be on any instance of a type. Types don't have to be
> > GObjects. (This is a bit silly IMO, but that's how it is.)  The
> > "instance" here is simply the object emitting the signal.
> 
> Perhaps what i am trying to say is that the signal's itype/instance only
> determine the signal's scope.  The emitters and receivers of a signal
> may or may not be part of the signal's instance.  To contrast, the
> documentation seems to imply that the signal is probably emitted by
> the instance.

which is correct.
a signal usually is created in the class_init function of a certain
instance type, and later it is emitted for instances of (or derived
from) that type.

---
ciaoTJ