Joe Pluta wrote:
...
I'm still a little concerned about the mechanics - is the 16MB limit per module? Per bound program? If it's the former, the compiler I wonder if the compiler can't catch it. If the latter, shouldn't it be detected during the bind? If neither, if it's at the job or activation group level, then it's a subtle and potentially very hard to debug problem.


At compile-time, the automatic storage for any one procedure cannot exceed 16MB. At run-time, the total automatic storage used by all procedures currently on the call stack cannot exceed 16MB.

The compiler _could_ catch some cases of too much automatic storage in a procedure, but it couldn't catch them all, because some of them are added after the compiler has generated its code.


This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 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.