QuantLibMma license

[Niels Elken Sønderby]

Hi Ferdinando

> I missed the announcement. Was it my fault, or it just wasn't distribute?
It wasn't distributed in the first try. I had used a different e-mail, and
was
rejected because of "Post by non-member to a members-only list". Should
be fixed now.

> #if QL_HEX_VERSION < 0x000302a1
I should definitely add this check together with an instruction on the web
page, so people trying to compile don't get ugly surprises.

> Since you adopted the QuantLib licence I would propose you to put
> QuantLibMma into a new module of the general QuantLib CVS repository at
If the project develops to a bit more than the present "proof-of-concept"
stage,
I will probably do this. Also if someone wants to contribute significant
amounts
of code, this will probably be the easiest. For now, I'll just let the
SourceSafe/CVS/versioncontrol be my local harddrive. (Also consider as I'm
only with a modem-connection, making uploads through CVS a bit clumsy.)

Cheers... Niels

----- Original Message -----
From: "Ferdinando Ametrano" <[hidden email]>
To: "Niels Elken Sønderby" <[hidden email]>
Cc: "QuantLib-dev" <[hidden email]>; "Luigi Ballabio"
<[hidden email]>
Sent: Wednesday, May 14, 2003 12:28 PM
Subject: Re: QuantLibMma license


> Hi Niels
>
> >as announced on the QuantLib user mailing list, I just released a first
> >limited version of QuantLib for Mathematica.
> I missed the announcement. Was it my fault, or it just wasn't distribute?
>
> >I have simply used the QuantLib license as I prefer a BSD style license.
As
> >a consequence I have copied the text from
> >the QuantLib C++ sources, modified it slightly and used it in my own
> >.m-files and .cpp-files. This text includes your e-mail-address.
> >I would like to ask you to have a look at this text, and also the
> >License.txt and tell me if everything is fine with you.
> Ok, you can also substitute my address with yours
>
> >Obviously, also any suggestions for improvements concerning the license
or

> >the QuantLibMma package in general will be highly appreciated.
> On a medium/long term strategy I think that QuantLibMma maintainance could
> be demanding, especially if you don't synch it with the current Quantlib
> CVS code.
> Which version of QuantLib have you used for QuantLibMma?
> I suggest you add a check somewhere in the main header file as in:
> #if QL_HEX_VERSION < 0x000302a1
>      #error using an old version of QuantLib, please update
> #endif
>
> Since you adopted the QuantLib licence I would propose you to put
> QuantLibMma into a new module of the general QuantLib CVS repository at
> (quantlib.org) SourceForge: this would allow everybody to follow any
> intermediate development between QuantLibMma releases.
> QuantLib-Python, QuantLib-Ruby, etc are also there at SourceForge.
> Should you go with (quantlib.org) SourceForge you could just use the
> verbatim text of the QuantLib license
>
> I will also add you email address to the quantlib-dev mailing list (in CC
> here): it is a message for back-channel communication between the most
> active QuantLib developers
>
> As for the packaging I cannot comment, since I'm not a Mathematica user.
>
> Anyone has additional/different suggestions/comments? Luigi?
>
> ------------
> ciao -- Nando
>