hello, Luigi Ballabio wrote: [snip] >> 3] The SWIG sources did not contain the BarrierOption instrument >> (although they did have Barrier::Type), and also a few pricing engines. >> I've added those that I required; some may still be missing. > > Yes, sadly the bindings tend to stay behind the library. > I'm willing to take up maintaining the SWIG bindings (although I'll be using mostly the Python ones for now). Also, it looks likely that I'll be attempting to develop a QuantLib Java/JNI binding for my company sometime in the future, which I can (hopefully) contribute back to QuantLib. >> BTW, are there any plans to add a Python-specific documentation similiar >> to wxPython using Epydoc? I imagine some change in the SWIG bindings or >> generation options would be needed. > > Last I heard, someone was working on patching SWIG to generate > docstrings in the bindings. That would allow PyDoc to work some magic. > But I don't know whether that is ready for prime-time. The patch for that is already in SWIG CVS; see http://tinyurl.com/3zl9n BTW, does anyone know when is the release of QuantLib 0.3.8 expected? Thanks, Ashish
"This e-mail message may contain confidential, proprietary or legally privileged information. It should not be used by anyone who is not the original intended recipient. If you have erroneously received this message, please delete it immediately and notify the sender. The recipient acknowledges that ICICI Bank or its subsidiaries and associated companies, (collectively "ICICI Group"), are unable to exercise control or ensure or guarantee the integrity of/over the contents of the information contained in e-mail transmissions and further acknowledges that any views expressed in this message are those of the individual sender and no binding nature of the message shall be implied or assumed unless the sender does so expressly with due authority of ICICI Group.Before opening any attachments please check them for viruses and defects."
| Free forum by Nabble | Disable Popup Ads | Edit this page |