I believe that we cleared up the license issues in recent private mails. Did we adequately clear up the license issues? In order to get the e_float core in the sandbox, we need to define how much we would initially like to have in the core. I might suggest: - The real data type e_float, its base class and its interfaces to the big-number back ends. - The specialization of std::numeric_limits<e_float>. - The complex data type (ef_complex) - Elementary transcendental functions (trig, power, log hyperbolic) for real and complex. - (optional) Possibly the Gamma function and Zeta functions for real and complex. This selection would limit the initial size of the e_float core in the sandbox to a few tens of files and no big ones. Would this initial selection be appropriate? Sincerely, Chris. From: John Maddock <boost.regex@virgin.net> To: boost@lists.boost.org Sent: Saturday, June 4, 2011 10:10 AM Subject: Re: [boost] Is there interest in e_float: Multiple-precision floatand special functions?
To move forward, I would welcome the core e_float (with addition of reference to Boost license terms in the program text - as normal Boost practice) to be put into the Boost Sandbox. This will allow us to have something concrete to try out and make more informed comments on exactly what Boostification we feel is desirable. (It will also allow us to get a definitive license statement of agreement from ACM before we get too far in. ).
Just to be clear, we would need to sort out the license definitively *before* any code went into the sandbox SVN. Pedantically yours, John. _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost