This really depends on the kind of code generation being used. There's "dumb" code generation, and there's a DSL.
In the "dumb" case, the input is usually some tabular data, and the code generator simply translates it to valid C syntax. It makes sense to say "it was written in C" in this case, although it's a bit moot since this is just data.
In the DSL case, the logic is actually coded in a different language, and the code generator translates it to C. Here it would be more difficult to argue that "it was written in C", because C just serves as a compiler intermediate language.
Naturally there are levels in between the above two, but the point is that it's difficult to judge without examining the actual module that was auto-generated.
true, though it's unlikely that you would launch a DSL. far more likely that a lot of the code being generated is lookup tables and the like. engineers that write this sort of fault tolerant related code will do a lot of things the 'dumb' way because it's often less error prone or easier to trace failures. a number of friends work on space related things, and there tends to be an emphasis placed on not being overly clever (i.e. practices like return values being true or false rather than enumerations, etc)
In the "dumb" case, the input is usually some tabular data, and the code generator simply translates it to valid C syntax. It makes sense to say "it was written in C" in this case, although it's a bit moot since this is just data.
In the DSL case, the logic is actually coded in a different language, and the code generator translates it to C. Here it would be more difficult to argue that "it was written in C", because C just serves as a compiler intermediate language.
Naturally there are levels in between the above two, but the point is that it's difficult to judge without examining the actual module that was auto-generated.