Yuri said: > The are more than one reason to avoid bundling a package with > more than > a reasonable default and a _simple_ api:
> With dynamic loading, we could be done with a very simple api, a base > theme (say gtk+ alike) and forget about it. Are we talking about some sort of dlopen-a-like system, maybe even with a C-callable API? (So as to dodge the c++ name-mangling issues across compilers.) If so, I'd agree (indeed I have code, somewhere, that wraps up the win32 dll loader to make it "look" like dlopen and friends, in a limited sort of way) but I worry about the constraints that a C API might bring to a C++ toolkit. Although not insurmountable, it is awkward. I get around that by allowing some C++ API, but that only works because I build everything with the same compiler. For random plugins built with different tools (particularly on win32 where there are more compiler choices...) things get tricky. I'm sure someone knows better than I do about this, however, so I'm happy to be enlightened! -- Ian SELEX Sensors and Airborne Systems Limited 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 mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
