🚀 go-pugleaf

In article <GRUNWALD.92Oct5144638@bullwinkle.cs.colorado.edu>, grunwald@bullwinkle.cs.colorado.edu (Dirk Grunwald) writes:
|> Currently, there's macros to make a field selection callback class &
|> file selection callback class,
 ...

|> However, I've found it easier to just specify the class w/o the generics...
|> 
|> The only problem is, I'd like to be able to use MI to do the same
|> thing. E.g., lets say I have a Glyph with represents some dialog
|> w/many call backs. I could inheriet from each of them & then pass one
|> pointer for all of the call backs.
|> 
|> But, if they all use the same ``callback procedure names'' (i.e. like
|> execute, above) then this won't work.

Even though the callbacks have the same name, they have
different signatures.  So I don't understand why multiple
inheritance would not work with the current definitions.