Yes, it can be copied for full compatibility. Note that we take a different convention on x64 that _ui and _si functions use 64 bit words instead of 32 bits. But for most functions this doesn't affect compatibility.
On 20 September 2017 at 12:30, Francis Andre <francis.andre.2...@gmail.com> wrote: > Hello > > I am porting on Windows a Linux application that is a consuler of the GNU > gmp library. Googling for GMP on Windows, I did not find any realistic GMP > packaging on Windows except the mpir library, which in my understandin is a > fork fo the GNU gmp library. So I choose to use the mpir librairy to > replace the GNU gmp one. But the include interface is different. The ported > application is referring the include gmpxx.h which is in fact the mpir.h. > > Thus can this 'mpir.h' include be renamed 'gmpxx.h' or copied to 'gmpxx.h' > so that a full compatibility be insured. By the way, the head of mpir.h is > as below > > /* gmpxx.h -- C++ class wrapper for GMP types. -*- C++ -*- > > Copyright 2001, 2002, 2003, 2006, 2008, 2011, 2012 Free Software > Foundation, > Inc. > > -- > 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.
