> > Also if you upgraded Boost.Signal to Boost.Signal2 you would also get > a healthy speed-boost as well (requires some code changes). Signals1 > has a lot of inefficiencies that hobble it down, hence the redesigned > Signals2 being vastly more efficient (and can be properly thread-safe > too if you so wish, unlike Signals1). >
The speed improvements are probably not worth switching to the new signals, as this is not the area where the library spends a lot of time. Better thread-safety would be a good thing (but the model of boost.signal suits current Wt fine). I haven't looked at signals2 yet; I hope it's a switch we can do under the hood without API changes. Regards, Wim. ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
