|
From: Luigi B. <lui...@gm...> - 2007-08-03 10:40:05
|
On Fri, 2007-07-27 at 09:57 +0200, DU VIGNAUD DE VILLEFORT FRANCOIS GASAPRD PHI wrote: > In our implementation market data and evaluation date changes are > propagated through the same channel (observers update methods). > > As we are properly trying to handle properly the evaluation date > changes this coupling is becoming more and more an hindrance (eg: the > Capstripper can no longer notifying lazily its observers). Can you elaborate? What is the problem? > What about having dedicated channels ? Though I’m sure that some of > us have already thought about this solution but what about using boost > signal library to implement the notification chain ? Any thoughts ? Yes, we might have a look at Boost.signal. But it would be a rather large refactoring, and lately I'm becoming more concerned with finalizing a 1.0 release, which calls for more stability instead. Frankly, I'd leave your suggestion for after a stable release. Later, Luigi -- Barker's Proof: Proofreading is more effective after publication. |