× 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.


  1.  Home
  2. MIDRANGE-L
  3. July 2015

Re: How does the i handle programs in memory using different methods?

On 7/20/2015 9:02 PM, D*B wrote:
... local static variables will behave diffrent than automatic variables with recursion and problems with static variables will arise if a procedure is ever called in a multithreaded environment, they won’t be threadsafe!
I would never use static local variables! If a variable is statefull, it should be moved up to global, to be prepared for further modularisation of a procedure (procedures tend to grow and never to shrink!).


Thread-safety issues are the same for local static and global static variables.

If you code the THREAD keyword in your H spec, your static storage will be thread-safe.

If you code THREAD(*CONCURRENT), each thread will have its own copy of the static variables, unless you code STATIC(*ALLTHREAD) on a variable. STATIC(*ALLTHREAD) variables are inherently thread-unsafe, whether they are global or local.


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.