From the user's point of view, a call of CM.autoload acts very much like the corresponding call of CM.make because the same bindings that CM.make would introduce into the top-level enviroment are also introduced by CM.autoload. However, most work will be deferred until some code that is entered later refers to one or more of these bindings. Only then will CM go and perform just the minimal work necessary to provide the actual definitions.
The autoloader plays a central role for the interactive system. Unlike in earlier versions, it cannot be turned off since it provides many of the standard pre-defined top-level bindings.
The autoloader is a convenient mechanism for virtually ``loading'' an entire library without incurring an undue increase in memory consumption for library modules that are not actually being used.