New answers tagged

-1

I've written and maintained a reasonably-sized commercial package in assembly language (40,000 lines of 16-bit code and 35,000 lines of 8-bit). It worked well and had zero bugs. The only inter-module communications possible were that a symbol (an address in program code or a data address in memory) could be declared public in one module and external in ...


2

A book could be written on this topic. I bet some have . . . It's hard to answer because each tool-chain has its own strengths, shortcomings and quirks. I must have structured different projects a half-dozen different ways, but I will mention the two that I've used the most. For almost all techniques, you need to partition the components adequately. The ...


0

The only way to archive that is to create good architecture. Then you can partition your software into components. For example, in C and C++, one component can be a library. Then in tools like sonar and jenkins, you can checkout just specific components, and do with them whatever you like.



Top 50 recent answers are included