On Sun, Jan 11, 2009 at 3:14 PM, Jürg Billeter <j...@bitron.ch> wrote: > * Generate two sets of header files > For each source file foo.vala, we could generate foo-priv.h in > addition to foo.c and foo.h and move the internal C API there. One > issue with this approach is that it clutters the source directory > with even more files. The compiler will always have to generate all > three files, even if some are empty, to not break build system > integration. > > * Generate one additional header file for the internal API > We could avoid generating many -priv.h by just generating one big > foo-priv.h file that contains the full internal. However, in some > projects you have a large internal API, for example, in applications > without plugin support. This means that rebuild performance would get > a lot worse. >
How about a combination of the above two? * Generate foo-priv.h for each foo.c and * Generate one additional header for *public* API That is, rebuild costs raise only when changing public APIs Vlad _______________________________________________ Vala-list mailing list Vala-list@gnome.org http://mail.gnome.org/mailman/listinfo/vala-list
