I am not certain what It all entails yet, but I will find out and write a proposal for Idea 2 (Doxygen comments.) Thank you for your feeddback.

On Mon, Mar 30, 2009 at 12:56 AM, Soeren Sonnenburg <sonne@debian.org> wrote:
On Mon, 2009-03-30 at 07:07 +0100, William S Fulton wrote:
> Soeren Sonnenburg wrote:
> > On Sat, 2009-03-28 at 10:19 +0000, William S Fulton wrote:
> >> Aaron Lebahn wrote:
> >>> Hello, I would like to apply as a student with Swig. I am most
> >>> interested in the Ideas 2, 5, and 6 on the Ideas list. I am experienced
> >>> in C++ and Java, and I am learning Python. Which of these three Ideas
> >>> are most needed? Thank you for your help.
> >> I'd say that the Doxygen comments (idea 2) is needed most and I'm keen
> >> on seeing this working well enough to make it into the production
> >> version of SWIG.
> >
> > BTW, how about converting all of swig internally to use stdint etc types
> > such as int32_t etc?
> >
>
> That is a possibility, but I'm not sure of what the benefits are given
> that there is support for the stdint types in stdint.h and I'm not aware
> of anything that is fundamentally broken.

Well one thing that is definitely broken are stdint based types on 64bit
machines. One has to manually specify -DSWIGWORDSIZE64 to get things to
work. Apart from that it is IMHO more clean to use stdint types
especially when you want typemaps for a range of types ...

But I agree doxygen support out of the box for all languages sounds like
a dream come true :-)

Soeren

PS: I am too busy currently, but I will try to come up with some
examples showing problems with stdint or stand corrected.
--
For the one fact about the future of which we can be certain is that it
will be utterly fantastic. -- Arthur C. Clarke, 1962



--
Aaron Lebahn
cplusplus328@gmail.com