I've only been using Fltk in pure C++ applications so far. Fltk is worth programming in C++ but I am not crazy about it. I don't like C either actually but it's easier to work with from other languages.
I have read some other posts in the past about creating a C API and it looks like the main issue is that it would bloat FLTK. I was thinking that if I was able to find a way to auto-generate a whole bunch of C functions that contain calls to all the C++ methods I could create the C binding and that if each was in it's own C++ file that contained the extern "C" brackets then there would be a mechanism to mitigate bloat. All of these files could be included from bloat.cxx during the early development stages and then bloat.cxx could be removed and the headers containing only the functions used could be included. It would be tedious to include 20-30 header files manually but I think that it would provide a lot of benefits too. I am wondering if GTK's gobject introspection feature will give non-C/C++ languages a boost as many languages bindings can be created much easier. It might increase Fltk's market share. I doubt that GTK would have been this popular if it was written in C++ from the start. Any similar efforts or pitfalls or general comments? -Patrick _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
