Re: Assertion vs Exception Handling
On Mar 16, 10:17 pm, Ian Collins <ian-n...@hotmail.com> wrote:
On 03/17/10 11:04 AM, James Kanze wrote:
If the code is insufficiently fast without optimization,
then turning on optimization is generally the first thing
you should do; it's by far cheaper than having programmers
spend time optimizing manually. But until it's proven that
the code is insufficiently fast without optimization, you're
better off avoiding it.
This may be the case for hosted code, but it generally isn't
the case for embedded applications. Optimisations affect more
than speed, they can also change the size of the generated
code. Every embedded project I've worked on recently used a
combination of optimisations for both speed and code size.
Agreed. That should read "insufficiently fast or too big".
When you are shipping low cost products, moving to a bigger
(in memory terms) or faster processor can break the budget.
I know. While a lot of my recent applications have only run on
a couple of machines (or only one), some earlier applications
has run one thousands (and in one case, 7 million) machines. On
those, you're willing to invest a lot of development time just
to gain one ROM on the PCB.
--
James Kanze