Yes, but Flint itself relies on the old version, and no one has time to fix it.
On 23 January 2018 at 13:23, Brian Gladman <b...@gladman.plus.com> wrote: > On 23/01/2018 11:58, 'Bill Hart' via mpir-devel wrote: > > Hi Brian, > > > > The history of the Flint issue is in this ticket here: > > > > https://github.com/wbhart/flint2/issues/338 > > > > I'm not sure if MPIR Windows users will actually *want* this fixed. But > > unfortunately, Flint relies on the old semantics, and can't be easily > > fixed, I think. > > Hi Bill, > > Since, in respect of the two functions involved, the current versions of > MPIR and GMP now use the same semantics, the GMP compatibility layer > must have a fix for this. > > Can this fix not be applied to the MPIR interface? > > Brian > > -- > 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 https://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 https://groups.google.com/group/mpir-devel. For more options, visit https://groups.google.com/d/optout.
