Hello, Bill. You wrote 16 апреля 2010 г., 12:23:43:
> What you suggest is to effectively maintain two versions of MPIR, one > version 2.1 the other 3. No, quite the opposite. I am talking about plugin-based framework where framework itself is 2.1, and some plugins are 3.0, some are 2.1 too. Here 'plugin' means either implementation of mpn-function or one of the higher layer functions. I don't know MPIR's internals good enough, but I thought that library is modular: i.e. you can change mpn internals without affecting higher layers and you can change implementation of some function without affecting another functions. > We did consider such an option, but it is much harder than it > seems, and we simply don't have sufficiently many contributors to > manage that, Could you point me out one or two of the difficulties? May be there is a way to workaround them... > there seems to be a lot of interest in contributing to a BSD > licensed library. Another individual I asked about this said they > thought it was a great idea and that one of the main things that > puts them off currently is the LGPL. What is wrong with LGPL as long as it is 2.1? Currently I see only one drawback - it can't be used in a BSD open source project. However, I know of no BSD open source project which may be interested in multiple precision. -- 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.
