[..] > > There are two, being: > > > > A) FLTK3_EXPORT void alert(const char *,...) __fl_attr((__format__ > > (__printf__, 1, 2))); > > B) FLTK3_EXPORT void alert(va_list, const char *); > >
const issues aside, (A) says there's an fl_alert() that takes a char* argument and some other arguments, while (B) says there's one that takes some arguments and a char*. Isn't that bound to be ambiguous in some cases? For instance, imagine <maybe const> char* a, b, c; fl_alert(a, b, c) No matter whether the declarations of (A) and (B) include const, won't there always be some combination of const/non-const a,b,c that makes the fl_alert call ambiguous? Or have I missed something? _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
