|
From: eric <er...@eh...> - 2004-10-31 22:31:55
|
> 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. Here are the revised docs: http://www.ehlers.plus.com/quantlib/quep011.html http://www.ehlers.plus.com/quantlib/quep012.html The latter proposes an approach for automatic generation of source code. The doc needs further revision but should be enough to get our discussion started. > 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. Great, and yes you got my name right. Unfortunately as I don't have Borland and VC7 I'll break these every time I add files etc., maybe it will be easier for you to leave them, and fix them once last thing before the release? > 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. OK, I'm happy to do the autoconf & documentation. I'll fix all *nix makefiles. > 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. I'll edit the final drafts of the docs to refer to 0.3.8. I've just attempted to commit a load of changes to cvs, I'm not sure if they've gone through. > 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? That address is fine, thank you. > How are you managing the QuantLib-cvs traffic ? ;-) The team certainly does keep busy :) Regards Eric |