> Make the wrapper support (the if (wrapper) sections and extra > members) > conditionally compiled in so that it only has any impact > (overhead) at > all if it was requested at compile time. Therefore the built > version of > the library on a system may not support code written around > the wrappers. > It isn't a perfect solution, but would allow building of a > compatibility > library that was a little less light-weight while still > keeping the core > of fltk3 on a diet.
Yup, I wondered about that - we add a FLTK3_LEAN_AND_MEAN option to the sources to build the fltk3 libs without the compatibility hooks in place, for those that don't require (or wish to avoid) the perceived overhead. But, I think this is premature optimisation at this stage: first, we should build it with the hooks in place, and then see how much it *really* costs us. Modern compilers may be able to elide the hooks a lot of the time, I think, so the impact may be less than people fear. If it transpires that we are taking a hit, *then* we implement the FLTK3_LEAN_AND_MEAN option. How does that sound? > I also feel that consideration should be given to using stl types in > favour of creating new, function duplicating types (I'm not accusing > FLTK of this at the moment at all, but wxString and QString are two > examples of types that just shouldn't exist in my world view. > std::string is there and should be used when it doesn't add too much > overhead. If std::string is too heavy, so are the replacements. Also > consider the use of new options that C++1x might one-day introduce). This has always been a tricky choice, almost a philosophical choice for us - the fast/light nature of fltk is attractive to embedded systems, which often have resource constraints and/or less complete compiler tool chains, that make things like STL and Boost something of a problem... But where do we stand on that these days? 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 mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
