[Quantlib-dev] Re: ObjectHandler, QuantLibAddin, and QuEPs

[eric <er...@eh...>]

Hi Nando, Hi All

Just a quick message as I'm running to catch a train.  In general I
agree with all of your points and I'll send more specific comments on
Monday, as well as a split QuEP11(/12?) and a draft design for the
automatic generation of code - I'll look at IDL.

Many thanks for your help, speak to you soon.

Regards
Eric


On Wed, 2004-10-27 at 17:18, Ferdinando Ametrano wrote:
> Hi Eric,
> 
> [I'm CCing QuantLib-dev and Jody Goldberg]
> 
> I've imported ObjectHandler as a separate module in the CVS. In order to 
> reflect this change we could split the QuEP you've submitted into two 
> separate QuEPs, one dedicated to ObjectHandler and the other to the rest.
> 
> I've added Borland, VC7, and Dev-C++MinGW support and/or project files for 
> ObjectHandler. I've added the copyright notice (please confirm that I've 
> spelled your name right) plus a couple of minor files and fixes.
> 
> It look like your ObjectHandler prototype is almost ready for a first 
> release. I might have introduced some problems with the *nix Makefile, but 
> you can check it out and fix them. Hopefully we could autoconf the project 
> before the release, add some Doxygen documentation, and I would provide a 
> Win32 installer.
> 
> As for the rest: I've renamed your ObjectClassLibrary as QuantLibAddin. The 
> CVS QuantLibAddin module includes the QuantLibAddin library plus all the 
> Addins and Clients (C++, Calc, and Excel). I've added Borland, VC7, and 
> Dev-C++MinGW (partial) support and/or project files, (some) copyright 
> notice, and some minor files and fixes. The code is updated to work with 
> the forthcoming 0.3.8 release and the current CVS trunk.
> Once again I might have introduced some problems with the *nix Makefiles: 
> please check them.
> 
> I've already granted you write access to the CVS, so please use the CVS 
> code base for any further development. When we'll publish the QuEPs we will 
> be referring to QuantLib 0.3.8, and the latest version of your code will be 
> available in the CVS for public inspections.
> 
> BTW I'm going to add er...@eh... to the QuantLib-dev mailing list. 
> Is it ok for you? Would you prefer a different address?
> How are you managing the QuantLib-cvs traffic ? ;-)
> 
> Jody: thank you for any help you can provide for Gnumeric. Are you 
> interested in joining the QuantLib-dev mailing list? Do you plan to 
> personally contribute to the Gnumeric version of the QuantLibAddin?
> 
> >What do you think about the autogeneration of code described under
> >"Notes"?  Jody and I agree that autogeneration is the way forward, if
> >you agree I'll do a design doc for that.
> I do agree that autogeneration is the way forward. I'm not sure 
> Python+config_file is the best approach, but I'm not an expert. What about 
> IDL definition and IDL compilers?
> 
> thank you very much for your contribution
> 
> ciao -- Nando
> 
> 
> Eric wrote:
> >I've revised the design doc, and the URL has changed:
> >
> >http://www.ehlers.plus.com/quantlib/quep011.html
> >
> >Here are the html and other files:
> >http://www.ehlers.plus.com/quantlib/quep011.zip
> >http://www.ehlers.plus.com/quantlib/quep011.tar.gz
> >
> >Please let me know if any revisions are needed.  You're welcome to edit
> >the doc directly if that's easier for you.
> >
> >Here's the code:
> >http://www.ehlers.plus.com/quantlib/ObjectHandler.zip
> >http://www.ehlers.plus.com/quantlib/ObjectHandler.tar.gz
> >
> >I'm new to QuantLib and Boost and I'm sure the code has much room for
> >improvement - all feedback is welcome.
> >
> >Regards
> >Eric