Re: [Adonthell-devel] SWIG 1.3.17

[joël vennin]

On Mon, 20 Jan 2003 21:03:01 +0100
Kai Sterker <address@hidden> wrote:

> Actually, I wanted to fix that Swig 1.3.17 issue today. I mean, how hard
> could it be to add a few extra constructors? :P
> 
> First surprise: all those classes _had_ constructors! After messing
> around for a while I finally turned on all warnings in Swig, and here's
> what I got:
> 
> C++ analysis...
> win_wrappers.h:517: Warning(403): Class 'win_image' might be abstract.
> No constructors generated. 
> win_wrappers.h:625: Warning(403): Class 'win_label' might be abstract.
> No constructors generated. 
> win_wrappers.h:655: Warning(403): Class 'win_write' might be abstract.
> No constructors generated. 
> win_wrappers.h:671: Warning(403): Class 'win_mapview' might be abstract.
> No constructors generated. 
> text_bubble.h:43: Warning(403): Class 'text_bubble' might be abstract.
> No constructors generated. 
> 
> So the question is why Swig thinks that those 5 classes might(!) be
> abstract? Any ideas? Could it be a bug of Swig? Or is it our fault as so
> often?

Hehe , it's just a swig bug, why you want the C++ code is not ok ? A class must 
be abstract if there has a "pure" virutal methode, but there is no "pure" 
virtual method ... C++ assign a default constructor for each class ...


 
> Kai
> 
> 
> _______________________________________________
> Adonthell-devel mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/adonthell-devel