GARTHWILSON wrote:
BigDumbDinosaur wrote:
Assembly is generally done a source file at a time.
I use INCLude statements which bring the other needed source-code files in, then only mention the main source-code file when calling the assembler.
As do I. However, the main source file for each program has to be submitted to the assembler. Currently I have 13 separate programs that I have written for POC, each of which would have to be reassembled if I changed the BIOS jump table. It would take some time, since the actual assembly processing time is only part of the total time needed.
Quote:
I have a friend who, until he retired recently, managed software projects so huge and involving so many programmers that they took around 24 hours to re-compile. What we do with our 65xx efforts will assemble the whole thing in a few seconds.
I have had experiences like that, although not involving multiple programmers. Back when I wrote a truck leasing and billing system for the Commodore 128 running on a Lt. Kernal hard drive subsystem I was working with around 100,000 lines of code. Assembly of the entire mess took about 8 hours. Needless to say, I did my best to avoid making any changes that would have required full reassembly. Once it was all working changes could often be made to a few source files and only those would require reassembly, reducing the development cycle time quite a bit.
I just ran POC's BIOS through the assembler to see how long it would take to assemble it. It took about 5 seconds to run through 12,218 source lines. The program that I am working on that generates an S51K filesystem analog takes about 8 seconds to assemble, and runs to nearly 20,000 lines spread out through a bunch of INCLUDE files. And I'm not even finished with it!