R:So far, it's been much easier to use ASM, specifically a macroassembler, with my library of macros, which I understand well enough to equal the comparable intrinsics of any compiler, and, as a result, I know the generated code is as fast and as dense as I require.
E:Finally the cat came out of the bag
R:As for the cat ... I have no idea what you mean
you "understand well enough" the above and do not, and have no intention of getting to "understand well enough" C etc.

Yes, I know what my macros do, how much code they contribute, how much time they require, and, since that's the case, and I already have them on hand, there's no need for a compiler.
That may be so, but why do you then argue with those that do have a need for a compiler

I'd take a look at a compiler if there were a reasonable way to evaluate it. That doesn't guarantee I'd buy it, though. It would have to be advantageous in some meaningful way for me to buy one.

T.T.T. and you do not want to. If it (as it did for me) takes a long time to get "up to speed" in C before the advantages shine, then, of course it is easy for you to just say "this is not worth it"

I'd take a look at a compiler if there were a reasonable way to evaluate it. The snake bites its tail here, if you are not fluent in C (i.e. have worked for years with 'some' compiler) you can not evaluate. Another issue here is that 'getting fluent' in C is almost impossible on a micro, it is many times faster on a PC, which is why I always recommend learning C (using Kochans book) on a PC before even writing the first C line for a micro.

Erik



T.T.T.
Put up in a place
where it's easy to see
the cryptic admonishment
T.T.T.
When you feel how depressingly
slowly you climb,
it's well to remember that
Things Take Time

Piet Hein