Re: Some questions about forcing recalculation

Posted by Andrew Kolesnikov on
URL: http://quantlib.414.s1.nabble.com/Some-questions-about-forcing-recalculation-tp12208p12214.html

Eric wrote:

"Not exactly.  Suppose Range B depends on Range A.  If A's inputs change, Excel
is smart enough to recalculate B, even if A's return value is unchanged.  In
the scenario I describe above, A's return value would in fact change on each
recalculation, as the update counter is incremented - my_obj#0000,
my_obj#0001, etc.  But even without that, B is still recalculated.  If you set
calculation to automatic then you don't even need to hit F9"

Sure, moreover this example doesn't conflict with my previous statement about
argument change. But, you see, if we discuss trader workbook it's absolutely
inconvinient to use range reference: there are a lot of instuments(objects),
which are created at start up and upgraded during whole day, and many functions
(different calculations, in fact, created in different workbooks) dependent on
these objects. So string reference (e.g. "my_obj") is more applicable in practice.

"ObjectHandler 0.9.6 includes an enhancement that also solves this problem.
The enhancement ensures that all object references are up to date.  Suppose
Object B depends on Object A.  Any time Object B is retrieved, OH checks
whether B is newer then A, if not, OH recreates B before returning it to the
user."

So, does it include support for dependecy functions, i.e. will funcion with
string reference f("my_obj", some static arguments...) be recalculated if
my_obj is updated?

"What is the class of your "my_obj"?  I have never witnessed a use case like
the one you describe.  Typically when an object is required globally, it is
something such as a term structure which can be created just once when the
application is initialized, and thereafter updated non-destructively."

It could be term structure, but dependency functions use string reference instead
of cell, so it doesn't matter.

Regards,
Andrew