> I think to communicate with external devices at the lowest level we were calling c code.
As someone who spent a few years maintaining the ada ->c code wrappers, our team would use I would say he's correct.
We used ada wrappers to make the system calls to c to do networking and unix ipc. While ADA can call c directly, we had to support HPUX and SUN so sometimes we had to write c code and call that (#IFDEF HPUX). This was a pain.
The package system was very good, especially at dividing work among a large team (30+ programmers).
We had a lot of fake external hardware simulators we used to test our code against. This worked well as long as our simulators worked like the actual external hardware. It did with some frustrating exceptions of course discovered during the final test.
Dealing with time is a pain in all languages (UTC vs GPS) I think sidereal time thrown in for fun.
I remember some of those procedures (design->code->integrate,formal test->ship) that DOD projects had. We counted SLOC (Lines Of Code), but thankfully our reviews never were based on them. Code reviews could be useful or just frustrating. I suspected somepeople were just difficult so they wouldn't be invited to as many of them
As someone who spent a few years maintaining the ada ->c code wrappers, our team would use I would say he's correct.
We used ada wrappers to make the system calls to c to do networking and unix ipc. While ADA can call c directly, we had to support HPUX and SUN so sometimes we had to write c code and call that (#IFDEF HPUX). This was a pain.
The package system was very good, especially at dividing work among a large team (30+ programmers).
We had a lot of fake external hardware simulators we used to test our code against. This worked well as long as our simulators worked like the actual external hardware. It did with some frustrating exceptions of course discovered during the final test.
Dealing with time is a pain in all languages (UTC vs GPS) I think sidereal time thrown in for fun.
I remember some of those procedures (design->code->integrate,formal test->ship) that DOD projects had. We counted SLOC (Lines Of Code), but thankfully our reviews never were based on them. Code reviews could be useful or just frustrating. I suspected somepeople were just difficult so they wouldn't be invited to as many of them
Interesting to hear others perspectives on it.