I can't talk for mac os x, or some of the more esoteric OSs having had
no exposure to them, (however I imagine Jason's solution should work
with anything unix based?), but windows does allow you to load DLLs at
execution time, see: http://www.codeproject.com/KB/DLL/loadingdll.aspx
or the MSDN
On Tuesday 20 October 2009 14:45:05 Dan Grayson wrote:
> That's a good thought, but returning 4.3.0-mpir as the gmp version
> number would be less likely to break routines that compare version
> numbers than returning mpir-4.3.0, especially when comparing to
> something like 4.2.1 that doesn't hav
That's a good thought, but returning 4.3.0-mpir as the gmp version
number would be less likely to break routines that compare version
numbers than returning mpir-4.3.0, especially when comparing to
something like 4.2.1 that doesn't have the extra characters. There
are lots of packages out there t
We need something that gmp and mpir have but is different , the only thing is
the version number but it is coded as just a number 4.3.0 etc , if is was
encoded as gmp-4.3.0 then we could use mpir-1.3.0 and all would be good. We
can not change the gmp version number as many/most? programs test
That won't help a program that was linked with gmp discover whether
mpir is impersonating it at run-time, because gmp doesn't export
mpir_version, and thus the program can't examine it, even if it's
there at run-time.
On Oct 18, 7:53 pm, Bill Hart wrote:
> The binary itself also exports mpir_ver
This won't help detect which library is actually in use at run-time,
because the macros are examined only at compile-time.
On Oct 18, 4:36 pm, Jason Moxham wrote:
> On Sunday 18 October 2009 21:34:40 Dan Grayson wrote:> Suppose I link a
> program dynamically with libgmp, and at run time
> > lib
Just got my Internet back :)
I wonder if there is an easy way to detect if the mpir.h include file is from a
different version than the lib library file ? , I mixed it up once (wrong paths
to gcc, set one path but not both!) and all sorts went wrong.
On Monday 19 October 2009 01:53:19 Bill
The binary itself also exports mpir_version, which is a char * giving
the version string, "1.3.0" in the case of the MPIR about to be
released. I guess this is not so useful unless you already know you
have MPIR and not GMP. But in the rare case where a user has screwed
up by having a gmp.h from G
On Sunday 18 October 2009 21:34:40 Dan Grayson wrote:
> Suppose I link a program dynamically with libgmp, and at run time
> libgmp is being impersonated by libmpir. Is there a (reliable) way
> for the program to tell?
>
> I ask, because I like to arrange the copyright message of Macaulay2 to
> di
