Re: Questions for eventual Python module

On tir, 2002-08-27 at 06:25, Manoj Kasichainula wrote:
> On Mon, Aug 26, 2002 at 05:52:16AM +0300, Timo Sirainen wrote:
> > On Sun, Aug 25, 2002 at 04:31:24PM -0700, Manoj Kasichainula wrote:
> > > I don't have irssi-signal handling working quite yet. The main thing in
> > > the way is that I need a good way to recognize the type of each
> > > structure pointer (server, window, reconnect, etc.) and map it to the
> > > python wrapper object I've written for it. I haven't quite parsed out
> > > yet how the Perl module does this yet; what's the easiest way to go
> > > here?
> > 
> > Perl uses docs/signals.txt and generates perl-signals-list.h from it, using
> > get-signals.pl. You'd probably do something similiar to that.
> 
> Hmmm. So modules that add their own signals couldn't have their signals
> processed by scripts?
> 
> Maybe in the future, each _REC could include a field with a magic number
> (or a string pointer) indicating the type. Then signal handling code
> could look at the magic numbers and convert them appropriately. I only
> suggest this because I know you're pondering a rewrite :)
> 

If a rewrite is consitered, it might make more sense to shift to
GSignals (as they no longer depends on gtk+ byt only glib). Rather than
adding introspection to the existing system.

Python allready has exelent support for GSignals.

./borup