> [..] > > > 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?
No, I think that's about right - and is pretty much what is happening, if you have a compiler that is picky about it... SELEX Galileo Ltd Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
