|
On Thu, 29 May 2003, Lim Hock-Chai wrote: > > Question: If those procedures are all in-line procedures. Would this > dynamic call cause performance issue? > To me, a dynamic call is one where the address of the procedure isn't known when the you call it the first time. For example, when you call a separate program, the library & object name are used to search the system for the program. Then, the program might have to be activated. Finally, you can get the address of the code, and run it. (This is, of course, all done for you under the covers) Whereas, in your case, the procedure was loaded when the program was loaded, since it's inside the program itself. The address is already known (since that's what you're using to call it!) so it doesn't have to do any kind of searching.... it just runs the code at that address in memory. So... I would not consider what you're doing a dynamic call. It should perform exactly the same as calling the procedure directly. The only extra time would be the time it takes to copy the pointer from the data structure to the pointer in your prototype. But, the time it takes to copy 16 bytes is insignificant, even on older, slower, computers.
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.