Re: tramp-compat-funcall -> compat-funcall?

[Stefan Monnier]

> The use case, I think, is "to provide compatibility with older Emacsen,
> I need a convenient way to call a function softly without compiler
> warnings if it doesn't exist." I think, based on the two examples I gave
> (`gnus-funcall-no-warning' was the other instance), that it's not an
> uncommon need, and it's better to provide it in a core facility than ask
> package maintainers to implement it.

There's  (if (fboundp '<foo>) (<foo> <bar>))  already (which is much
better than tramp-compat-funcall since it says explicitly what to do if
the function doesn't exist).

So the question is what to do for the use cases of
tramp-compat-funcall not covered by this if/fboundp idiom.


        Stefan