The intermediate forms of the program are generally kept in primary memory, and not saved to the file system.
[4][5][6][7][8][3][1][2] Examples of compile-and-go systems are WATFOR, PL/C, and Dartmouth BASIC.
[3] An example of load-and-go systems is the loader Anthony J. Barr wrote for the University Computing Corporation in 1968 that was replaced in the market by the IBM OS/360 loader in 1972.
These OS/360 loaders performed many of the functions of the Linkage Editor but placed the linked program in memory rather than creating an executable on disk.
Advantages of compile-and-go systems are: Disadvantages of compile-and-go loaders are: Compile-and-go systems were popular in academic environments, where student programs were small, compiled many times, usually executed quickly and, once debugged, seldom needed to be re-executed.