|
I'm a little unclear about one aspect of ILE. Consider the following: A procedure can be bound by reference or copy. If it's by copy then the executable code for the procedure is actually part of the program build. However the procedure is itself part of a module which may have module level declaration (files/variables). It's this module level stuff I'm unclear about. When the procedure is bound by copy, where is the module level stuff kept? Does an area of the executable get kept aside for these variables? What about the file declaration in the module? Are there any problems with the same file being declared in the calling program? If more than one procedure is bound from the same module is there only one set of module level memory set aside? Sorry for being a little vague about it. It's just that I haven't encountered any commentary on these sorts of questions. Thanks in advance Mike Pantzopoulos EIG-Ansvar Limited Tel : 61 (3) 8630 3193 Fax: ********************************************************************************************************* This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient, any use, disclosure or copying of this message is unauthorised. If you have received this message in error, please reply using the sender's email address. This footnote confirms that this email message has been scanned for computer viruses. EIG-Ansvar Limited does not accept liability for any loss or damage, whether caused by our own negligence or not, that results from a computer virus or defect in the transmission of this email or any attached file. EIG-Ansvar Limited - Australia (A.B.N. 21 007 216 506) Email : insure@xxxxxxxxxxxxxxxx Eig-Ansvar Limited - New Zealand Email : insure@xxxxxxxxxxxxxxxx *********************************************************************************************************
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.