×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 7/20/2015 4:16 PM, Kurt Anderson wrote:
I admit I don't have an exact understanding of local variables memory management, but my understanding was that if I have a procedure called a thousand, million, etc times, I should define its local variables as Static so it's note uselessly fiddling with memory every time it's called.
If you have not measured performance;
and have not analysed the measurements;
and do not have a precise bottleneck:
it's too early to tune performance.
With that in mind, I can't think of a place where I decided 'static or
dynamic?' based on runtime performance. I choose static variables when
I want to maintain some state across sub-procedure invocations. Which
is rare.
I'm not saying that static vs dynamic can't possibly be a performance
issue! I am saying that after measuring, and analysing, I have always
been able to bring performance well into the acceptable range without
having to worry about static vs dynamic variables.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.