Do we officially (want to) use "bool" in FLTK 1.3 ? There are some places in the code where it's used already [1], but AFAICT bool was not used in FLTK, or at least it was not the *usual* way to define boolean values. FLTK 2.0, however, uses bool frequently.
If we start using bool, are there known drawbacks (e.g. converting function arguments), or something else? At least it's only defined for C++ (not C)... Would there be any incompatibilities to be expected, if we changed some methods' API ? Any opinions ? Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
