Re: obsolete functions found during the build process

[Stefan Monnier <monnier@iro.umontreal.ca>]

> In general, replace the obsolete functions as the warning suggests.
> In some cases, the use of the obsolete function is justified, though.

AFAICT, there are indeed cases where using decode-coding-string instead
of string-to-multibyte is not really an option, but that means
"obsolete" is not really a good description.

Using with-no-warnings to mask obsolescence warnings is OK when we know
that the code is only kept for backward compatibility, but when there is
no good replacement, it's not a good solution.

So we should strive to provide valid alternatives for every use of
string-to-multibyte (or de-obsolete it, tho it's not my favorite solution).


        Stefan