Not to be too hard on the C messages, here's another example: CCN1101 Maximum spill size of &2 is exceeded in function &1.
Explanation Spill size is the size of the spill area. Spill area is the storage allocated if the number of machine registers is not sufficient for program translation. User response Reduce the complexity of the program and recompile. And that all seems reasonable. At least to me, I've made the assumption that "spill size" is not something that is part of the language, but is of the implementation, such that looking up "spill size" in the index of the Language Reference doesn't get you there. Then, if you have <insert here some reasonable percentage> messages like that, then they are best documented separately, and since you can't reasonably document only some messages, you'd need to document them all. Adjudicating "some reasonable percentage" is another issue, but not one I'd go to the wall on. It that is a tiny fraction, OK. Either documenting fully in the compiler or fully separately works. It is only the "fully" that should concern us, not which manual (if at all) it sits in. The content is important, the style is... the style. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
