Re: Conceptual problem solved by GOTO
Chris Bensler wrote:
> That is true in alot of cases but not always. More code can sometimes cause
> additional cache misses (I just learned what caches misses actually are the
> other day, thx Kat :) which actually make the optimization less efficient than
> the original.
>
> This can be seen in certain circumstances simply by rearranging a few lines
> of more-or-less unrelated statements. The outcome is identical, but the
> execution
> speed changes for what seems an inexplicable reason. I have often encountered
> this type of anomoly when doing benchmarks. changing the order of functions
> often produces radically different results, for example.
Absolutely. I just wanted to address the mistaken assertion that GOTO is
faster than structure code (which under the covers often is the exact same
code.)
A poor implementation can make a difference as well.
"Science is the belief in the ignorance of experts." - Richard Feynman
|
Not Categorized, Please Help
|
|
