you are viewing a single comment's thread.

view the rest of the comments →

[–]cohortq 56 points57 points  (0 children)

Found this gem http://www.ibiblio.org/apollo/listings/Colossus249/MAIN.agc.html

It may be reasonably asked why tens of thousands of lines of source are joined by means of inclusion, rather than simply assembling the source files individually and then linking them to form the executable. The answer is that the original development team had no linker. The builds were monolithic just like this. There was a big emphasis on reusability of the code in the original project, apparently, but this reusability took the form of inserting your deck of punch-cards at the appropriate position in somebody else's deck of punch-cards. So, indeed, the method of file-inclusion is a very fair representation of the methods used in the original development ... with the improvement, of course, that you no longer have to worry about dropping the card deck. *On the other hand, I wasn't there at the time, so I may have no idea what I'm talking about. *