> > This is simply assuming -standard practice- ... in both cases > > If you consider large, requirements-driven, front-loaded, traditional > projects as the baseline for Ada, I get to pick Microsoft as the > baseline for C. Now let's talk about risk, schedule slips, late > deliveries, crashing software and products that the users hate. :-) MickeySnot does have one advantage over most Ada projects: They don't have outside customers to negotiate requirements with. And if the programmer codes something different than what he was expected to, the usual response is not "Fix it" but "That's OK, it looks cool and the users won't notice the inconvenience before buying it." > > Don't say "The Ada people could have done it the same way as the C people." > > That is not the way anyone is teaching them to do it. C people are being taught things that make C popular, while making software more expensive and less reliable. I am sorry about the first part, but I am NOT sorry that Ada folks are not being taught the last part.