Warnings in GMP.H, and potentially more serious problem

delta trinity deltatrinity at hotmail.com
Sun May 16 13:52:11 CEST 2004

>From: Torbjorn Granlund <tg at swox.com>
>"delta trinity" <deltatrinity at hotmail.com> writes:
>   That solution seem to work.  I don't have warnings anymore.  I wander if
>   MSVC would have give the same warnings.  I don't know as I don't have 
>   anyway...
>   If you say that it's the option that will be kept, I could make the 
>   to the file I've put on my ftp server (pre-compiled shared library), in 
>   erratum directory for example.
>I think that would be a mistake, since this is no GMP bug.
>The error is in the wolf crying compiler.

Humm, it depend on which side you look at it.  It's probably Borland 
specific.  I know that you probably can't account for every compiler's 
moods.  Though, my point was just that if the correction gave by Kevin will 
end up in the next GMP rev, I could have made the modification.

On the other side, I do understand that it's probably not the best option to 
put a second gmp.h online, especially for support.  I beleive that having 
several different gmp.h could be confusing and probably not desirable.

Though, if someone complain about those warnings, another option could be to 
tell them to include a modification to disable warnings in their source 
code, as #pragma.

#ifdef __BCPLUSPLUS__
#pragma warn -ccc
#pragma warn -ngu



Best Restaurant Giveaway Ever! Vote for your favorites for a chance to win 
$1 million! http://local.msn.com/special/giveaway.asp

More information about the gmp-bugs mailing list