Re: Removing some workarounds for big integers

[Philipp Stephani]

Am Mo., 22. Apr. 2019 um 20:57 Uhr schrieb Paul Eggert <eggert@cs.ucla.edu>:
>
> On 4/22/19 8:40 AM, Philipp Stephani wrote:
> > I've checked some of the remaining uses of CONS_TO_INTEGER. It seems
> > some of them we can replace right away. For some others the
> > documentation requires a number; we can detect integral floats for
> > them, but should deprecate the float usage.
>
> It sounds like a good idea to move in that direction. However, wouldn't
> it be simpler to modify cons_to_unsigned and cons_to_signed to issue
> warnings now, for every argument that is not an integer?

I don't think such warnings would work that easily. They would only be
shown to the end user, not the developer making the deprecated call.
Most of the time the conses come from some other function and the
developer just passes them on.