|
Hi Scott. Thanks for the info. <snip> > if your #1 requirement is performance, using an ordinary reference parm > would obviate the need to pass by value, since you can get & operate a > pointer to a ref parm, as long as it's not const. </snip> I was not aware that was possible. If I set up the module to accept a 140 Alpha parm, non-CONST, passed by reference, I can get a pointer to that parm, and build data structures based on that pointer? Well, I just answered my question by trying it... I thought that if a parameter was passed by reference, because the address was in the main module's pointer space, that you couldn't get a pointer to it from a called module. Where did I get that idea? This will make things much more efficient. Thanks! <snip> > If the goal is to get the data into a data structure, why not make the > parameter a data structure in the first place? Doing in that way, you > could pass by const reference without any problems. </snip> This is a set of several modules that analyze areas of the text report line. So each module defines a couple of data structures, to analyze these different areas. I wanted to simplify the main module, which will simply be handing the report lines to the appropriate module, and receiving back a data structure with a counter, and three output record data structures, as each line can contain 0-3 accounts. -- "Enter any 11-digit prime number to continue..."
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.