no calling range named...

[Aurelien Chanudet]

Hi Eric, hi all,

Let's consider the following sequence of actions :

1. Open Excel.
2. Open a new workbook.
3. Create an object (let's call it "object O")
4. Save the workbook (let's call it "workbook W") and close it.
5. Open a new workbook and call ohCollectGarbage().
6. Open workbook W.
7. Try to recreate object O.

This leads to the following error :
"qlSomeFunction - No calling range named _xxxxx"
where _xxxxx stands for the suffix appended to the name of object O as
of step 3.

I am using QuantLibXL 0.8.0. Am I doing something wrong ?

Thanks,
Aurelien

-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
QuantLib-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quantlib-users

[Eric Ehlers-2]

Hi Aurelien,

Apologies for the delay in responding to your message below.

> Hi Eric, hi all,
>
> Let's consider the following sequence of actions :
>
> 1. Open Excel.
> 2. Open a new workbook.
> 3. Create an object (let's call it "object O")
> 4. Save the workbook (let's call it "workbook W") and close it.
> 5. Open a new workbook and call ohCollectGarbage().
> 6. Open workbook W.
> 7. Try to recreate object O.
>
> This leads to the following error :
> "qlSomeFunction - No calling range named _xxxxx"
> where _xxxxx stands for the suffix appended to the name of object O as
> of step 3.

I am working on a medium-sized enhancement to the design of ObjectHandler.
 At present, there are certain series of events which can lead to objects
being orphaned in memory - not quite leaked, but effectively the same
thing.  The enhancement would prevent this error and I hope to include it
in the next release.

Part of the enhancement would be to rework some of the garbage collection
code which contains the bug that you found above.  So I will ensure that
the bug is fixed as part of that project.  Many thanks for your detailed
description of the problem.

Regards,
Eric




-------------------------------------------------------------------------
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-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quantlib-users

[Eric Ehlers-2]

Hi Aurelien,

On Thu, December 13, 2007 10:44, Aurelien Chanudet wrote:

> Hi Eric, hi all,
>
> Let's consider the following sequence of actions :
>
> 1. Open Excel.
> 2. Open a new workbook.
> 3. Create an object (let's call it "object O")
> 4. Save the workbook (let's call it "workbook W") and close it.
> 5. Open a new workbook and call ohCollectGarbage().
> 6. Open workbook W.
> 7. Try to recreate object O.
>
> This leads to the following error :
> "qlSomeFunction - No calling range named _xxxxx"
> where _xxxxx stands for the suffix appended to the name of
> object O as
> of step 3.
>
> I am using QuantLibXL 0.8.0. Am I doing something wrong ?

A fix for this bug has now been applied to the subversion tree
for inclusion in the next release.  You can also fix this bug
in your local copy of the 0.9 (or 0.8) ObjectHandler source by
uncommenting the destructor of class CallingRange.

Regards,
Eric



-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
QuantLib-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quantlib-users