Binary executable size and execution time related to code structure are a non-issue by at least an order of magnitude.> Theoretically this type of component software architecture could also help > divide up the work/responsibility of your development group as well as > defining the roles of the software components. >We are trying to keep to this type of division of code, but there are costs in terms of binary executable size and execution time that need consideration, so nice clean breaks by doing APIs and function calls can be difficult. But code is much easier to maintain when broken up, so we do what we can. Dave
I do quite firmly believe that when a project is simple enough that one person is capable of writing it, it should be written by one person. Many projects do eventually get beyond that point, but it is good strategy to try and stay in the one-man-software-development range.
Flight control software, even for orbital vehicles, should certainly be in that range.
A second (or third...) pair of eyes to CHECK the code is a good thing, but having two or three people write code that could have been written by one person is a bad thing. It really didn't take all that much time for me to write all of the software we use.
John Carmack
_______________________________________________
ERPS-list mailing list
[EMAIL PROTECTED]
http://lists.erps.org/mailman/listinfo/erps-list
