Re: byte compiler warnings when bootstrapping

[Dan Nicolaescu]

David Kastrup <address@hidden> writes:

  > Dan Nicolaescu <address@hidden> writes:
  > 
  > > Stefan Monnier <address@hidden> writes:
  > >
  > >   > > With that and with adding a few more (eval-when-compile (require 
'blah))
  > >   > 
  > >   > What is the use of (eval-when-compile (require 'blah)) in this 
context?
  > >   > I expect it's the wrong solution.
  > >
  > > When the number of warnings for undefined functions is too high it
  > > might be better to just require the package that defines them. But you
  > > might be right...
  > 
  > But how do the functions actually get defined at runtime?

Autoloading

(defun foo ()
  (info)
  (Info-read-node-name) <- this gets a byte compiler a warning,
                           but it is defined at runtime.