Hello, Bill. You wrote 16 апреля 2010 г., 15:07:18:
> The things wrong with LGPL: > * the number of contributors is too small even after two years of > working on this project > * companies are suspicious of it - worried the license will be changed > to GPL (I know this for a fact, I'm not surmising) > * if we use version 2.1 we can't use code from GMP and contributors > who refuse to use v3+ only (of which there are numerous) > It's BSD or v3+. We don't have any other viable options. And we've > demonstrated that. If MPIR was going to get piles of regular > contributors, we would have done by now. Thanks for the clarification. One more question: what's with interface of the new library? Will it be close to the GMP's one? That would make porting existing applications much more easier. Of course, there are things that are just source of confusion. It would be good to drop them from new library. For example: * inconsistent sizes of mp_exp_t/mp_bitcnt_t/... Sometimes they are 4, sometimes they are 8 (depending on compiler, OS and CPU). It makes writing cross-platform programs harder. Using GMP from another languages becomes harder too. Many modern languages aim to be platform-agnostic, i.e. program should work independently of the 32/64 bit issues. But it is hard to achieve when underlying GPM API changes when moving to another platform. C# program, for example, works as 32-bit under x86, but it works as 64-bit under x86_64. * lack of normal error handling (out of memory, division by zero, mpf_t underflow) -- With best regards, Sergey mailto:[email protected] -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en.
