Posted by
Ferdinando M. Ametrano-3 on
URL: http://quantlib.414.s1.nabble.com/destructor-performance-observables-with-large-observer-lists-tp8926p8928.html
On Sat, Jun 25, 2011 at 5:48 PM, Plamen Neykov
<
[hidden email]> wrote:
> wouldn't it be simpler just to use std::set<Observer*> and save you the trouble with the long id or am I missing something here?
great minds think alike... as a matter of fact in the trunk it has
already been switched to std:set on June 7th :-)
see
http://quantlib.svn.sourceforge.net/viewvc/quantlib?view=revision&revision=17788I was more concerned with possible non-unique elements than
destructor's performance reason, and that's why I would keep it at
std::set instead of having it as template parameter.
Roland could you confirm that the trunk solution is OK for you?
BTW in the current trunk there is a MAJOR performance improvement if
you work in a real time environment with many changing rate quotes
between recalculations: I patched a bug which triggered many useless
notifications
thanks to all for the report and help: it's refreshing to have
contributors really stressing the library.
ciao -- Nando
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2_______________________________________________
QuantLib-dev mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quantlib-dev