If time-to-market is critical, and maximizing profit isn't, and volume is low, then allowing larger code-space, and more machine cycles could be an engineering decision. Normally, however, such decisions aren't made by engineers.

Many times, people use HLL because their development time and effort are reduced. Often "doing it right" isn't as important as doing it quickly. It's the old "get in, get paid, get lost" thing.

Bear in mind, please, that I've not said one should never, Never, NEVER use HLL's. I've merely said that one shouldn't use HLL if he isn't "UP" to the task of doing it in ASM. There are often bits of code that would be much better (safer, smaller, faster) written in ASM, even if under the control of a program written in HLL. After all, if one can't program in ASM, one can't program. That doesn't say it's the only way.

RE