Posted by
Simon Ibbotson - Straumur on
URL: http://quantlib.414.s1.nabble.com/Non-copyable-curves-tp12013p12021.html
I did think of that, but the new functionality I submitted
(LocalBootstrap) relies on other information than just the data vectors
(information created during the curve-stripping process).
I'll continue testing this - unless you've got a particular preference
for factory classes over polymorphic cloning?
Simon
-----Original Message-----
From: Luigi Ballabio [mailto:
[hidden email]]
Sent: 30 May 2008 15:34
To: Simon Ibbotson - Straumur
Cc:
[hidden email]
Subject: RE: [Quantlib-dev] Non copyable curves.
On Thu, 2008-05-29 at 10:50 +0000, Simon Ibbotson - Straumur wrote:
> For this improvement (copy-constructors for curves), I've developed
some
> code for this method. The current copy behaviour is to keep the
linkage
> to the original Interpolation::Impl object. We need to create a new
> object derived from Interpolation::Impl and link the new object to a
new
> vector of data.
Simon,
it's probably easier than that. We can just use the interpolator
(which
the curves store) to recreate the interpolation based on the
newly-copied data vectors.
Luigi
--
If you can't convince them, confuse them.
-- Harry S. Truman
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/_______________________________________________
QuantLib-dev mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quantlib-dev