On Apr 18, 1:55 am, "Sisyphus" <sisyph...@optusnet.com.au> wrote:
> ----- Original Message -----
> From: "Cactus"
>
> > I don't see how this could be outside the jurisdiction of those who
> > forked the MPIR version of GMP.
>
> Yes - as regards MPIR, you are free to implement whatever bits and pieces
> you choose. It's just that when one builds with --enable-gmpcompat, one
> (naively) expects full compatibility with gmp. One doesn't expect the range
> of functions provided to have been censored.
>
> But one soon discovers the errors of one's expectations ... and adapts.
>
> Cheers,
> Rob
A good point Rob - we should really call it --enable-
maximumgmpcompat :-)
Brian
--
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To post to this group, send email to mpir-devel@googlegroups.com.
To unsubscribe from this group, send email to
mpir-devel+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/mpir-devel?hl=en.
