Except that I've been trying to make sense of what SDCC is really supposed to contain/provide for the user yet simply haven't. I know it's a big job creating a document for a project, but, the doc has to be right.

In order to do that, you can't be a programmer. Too often, I've seen programmers at work and heard them say, "Gee ... that's cool!" describing their own work. Such surprise and amazement shouldn't arise from within one's own effort! Clearly such work was done ad-hoc rather than in conformance to a specification. If the spec' doesn't precede the coding, and if the documentation doesn't precede the specification, then there's no firm basis.

The other thing, of course, is that I've written fewer than 100 lines of 'C' this year, and wrote less than that last year. I don't know enough about 'C' compilers to understand a well-written document, let alone what's out there. I did take a continuing-ed course in 'C' a decade or more ago, though, just to force myself through the process, at one of the local universities. I even bought a 'C' compiler for the 805x, but have never used it. I guess I'm a slave to ASM.

RE