It seems to me that we keep trying to remove obsolete GMP symbols from
mpir.h only to find that we have to put them back in again.
But if we put them back in, nobody then bothers to update their code
to remove them.
We hence need to do something that makes it evident that an obsolete
symbol is in use but also provides some incentive to remove any
dependence on it.
Instead of adding the symbols back into mpir.h (actually gmp_h.in),
why don't we publish an additional include file called, for example,
'gmp_obsolte_symbols.h' that people have to include if their code
depends on obsolete symbols?
If a compile with mpir.h fails we can then suggest that this may be
because they are using obsolete symbols and might hence need to
include 'gmp_obsolte_symbols.h'. There is then a signal of obsolesence
and a small incentive to remove the nuisance of an extra include.
Brian
--
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/mpir-devel?hl=en.
