Re: bytecomp warning for CL functions

[Dave Love]

Richard Stallman <address@hidden> writes:

>     I had installed a hack that tries to notice when you call a function
>     that will not be available at runtime (because the library
>     was loaded via (eval-when-compile (require 'LIB)) as is done for CL).
> 
> If you can make your code superior to Dave's code that I installed and
> then built on, please go ahead and put it in.

As far as I know, they're different things.  My code was specifically
testing CL stuff, even if it would be present at runtime, whereas
Stefan's would check for problems with functions not being available
at runtime generally.  (It never seemed to warn me usefully anyway,
but presumably that was because it was buggy.)

> His code has a list of specific CL functions in it,

That's only a few that are aliases and would otherwise escape.

> and also checks the function name.
> If your code check both kinds of cases and handles both properly, it probably
> does everything right.