Re: Follow-up to: Signals and malloced memory



> > gtk_marshal_INT__POINTER_INT_INT   ...and...
> > gtk_marshal_INT__INT_INT_POINTER   ...and...
> > gtk_marshal_INT__INT_POINTER_INT   

>  - decide what args your signal has
>  - make the marshaller match

	Yeah, it occurred to me that an easy, "natural" API for the object
is much more important than minimizing the number of marshallers.

> > gtkmarshal-extensions.h
> > gtkmarshal-extensions.c

> Just stick them in with your object implementation.

	I wrote them yesterday, and just created the separate .h and .c
files.  Now I'm too lazy to change it :)


--Derek



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]