LOADCOMP turns off subsequent (FILES (SOURCE) ...

[masinter]

I still believe it is unexpected/wrong behavior that if you (FILESLOAD (LOADCOMP) X) and then do (FILESLOAD (SOURCE) X) that it does NOT load the complete source because (some part of it) is already loaded.

Originally posted by @nbriggs in #733 (comment)

[nbriggs]

So (FILESLOAD (LOADCOMP) ...) says "Load the file with LOADCOMP? rather than LOAD. Automatically implies SOURCE". LOADCOMP? says similar to LOADCOMP but doesn't load it if it has already been LOADCOMPed. LOADCOMP says "Performs all operations on FILE associated with compilation, i.e., evaluates all expressions under a DECLARE: EVAL@COMPILE, ... Thus if building a system composed of many files with compilation information scattered among them, all that is required to compile one file is to LOADCOMP the others"