|
From: Tito I. <tit...@ya...> - 2008-05-08 19:28:01
|
I think we may be overlooking a pretty obvious solution here: http://puppetmastertrading.com/images/ObviousSolutionToQuantlibDevBottleneck.jpg Luigi Ballabio <lui...@gm...> wrote: On Thu, 2008-05-08 at 15:08 +0000, Simon Ibbotson - Straumur wrote: > Whilst I'd love to see what many other people are working on, I'm not > sure how this would work... a lot of contributions change the existing > codebase - so you'd either have duplicate code in the ql/contrib folder > or it would be purely for new classes. True, it wouldn't work if contributions change the existing classes. Those (or part of them) would have to be integrated with the main library. However, most contributions I received were new classes. I was thinking of those as going into the experimental folder. Luigi -- Newton's Law of Gravitation: What goes up must come down. But don't expect it to come down where you can find it. Murphy's Law applies to Newton's. ------------------------------------------------------------------------- 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-dev mailing list Qua...@li... https://lists.sourceforge.net/lists/listinfo/quantlib-dev |