Hi Bill,

Here it is

    https://github.com/wbhart/mpir/pull/164

That's sad that you lack candidates for developments. I will try to 
advertise the position. Is there a website for it?

Vincent

Le lundi 2 novembre 2015 10:27:48 UTC-3, Bill Hart a écrit :
>
> Hi Vincent,
>
> yes please do provide a pull request against master to port the GMP code.
>
> I'm afraid I haven't found time to get back to MPIR in a while. We are in 
> an extremely busy state here where I work at the moment, and unfortunately 
> this is likely to continue for about 3 months if not longer. But we will 
> eventually get back to MPIR.
>
> To be honest, it would be better if someone else stepped in to continue 
> maintenance of MPIR in the short term. My time is divided between too many 
> projects at the moment. We also have money to hire someone to work on MPIR 
> (in particular assembly optimisation) for a year starting March 2016. But 
> so far no one has applied who has a Masters, which is a hiring requirement 
> here. Sigh.
>
> Bill.
>
>
> On 2 November 2015 at 14:19, <20100.d...@gmail.com <javascript:>> wrote:
>
>> Hola,
>>
>> Anything new about your waiting commits? I can provide one to port the 
>> gmp code for comparing mpz/mpq.
>>
>> Vincent
>>
>> Le mercredi 2 septembre 2015 20:58:06 UTC-3, Bill Hart a écrit :
>>>
>>>
>>>
>>> On 3 September 2015 at 00:05, <20100.d...@gmail.com> wrote:
>>>
>>>> Hello,
>>>>
>>>> The prototype for mpq_cmp_z has been accepted by GMP. The code can be 
>>>> found in the last commits. Though they told me to be careful as the name 
>>>> of 
>>>> the function will only be fixed for the next release.
>>>>
>>>
>>> It should be straightforward to add this code to MPIR. There's nothing 
>>> particularly different about the mpq interfaces in MPIR and GMP, so the 
>>> code may work almost unmodified.
>>>
>>> If I recall correctly, we aren't quite finished with 2.7.0 patches. We 
>>> have some Windows ones to go in, and there's also an AUTHORS update. Once 
>>> that is out of the way, we can start pushing features into trunk again.
>>>
>>> I'm quite busy for the next 2-3 weeks, but around that time we should be 
>>> able to move forwards again.
>>>
>>> Thanks for discussing it with the GMP guys. I did follow some of the 
>>> discussions, and it looks like they did a very thorough job.
>>>
>>> Bill.
>>>  
>>>
>>>>
>>>> How should I proceed if I want to port it to mpir?
>>>>
>>>> Best,
>>>> Vincent
>>>>
>>>> -- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "mpir-devel" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to mpir-devel+...@googlegroups.com.
>>>> To post to this group, send email to mpir-...@googlegroups.com.
>>>> Visit this group at http://groups.google.com/group/mpir-devel.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "mpir-devel" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to mpir-devel+...@googlegroups.com <javascript:>.
>> To post to this group, send email to mpir-...@googlegroups.com 
>> <javascript:>.
>> Visit this group at http://groups.google.com/group/mpir-devel.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"mpir-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mpir-devel+unsubscr...@googlegroups.com.
To post to this group, send email to mpir-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/mpir-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to