标签：function allocation about returning object large memory data

When a large data chunk is to be generated by a function, it can be either acquired from the function’s return value or passed by reference or pointer as an in/out variable. According to my development experience, I have summarized the following principles for choosing the appropriate solution.

• Even though, there may be compiler optimization when a large object is used as the function’s return value, it is still not recommended. Instead, the large object should be passed to the function as a mutable reference, which can hold the returned data.

• For the sake of improving the overall efficiency by limiting the number of times of memory allocation and releasing, the memory for the returned object should be allocated outside the working function, if its size can be predetermined. In this way, if the memory of this object can be reused, only one time of memory allocation and releasing is needed.

• For the sake of user convenience, like matrix and vector operations in Octave, it is obvious that the memory allocation is performed inside the working function.

• A practical design of the numerical library depends on whether it aims to achieve low level operations with high performance or realize a high level user friendly interface. The former prefers memory allocation outside the working function, while the latter inside.

• LAPACK is a typical example of low level numerical library, where the memory for all data and work spaces is predefined and allocated.

标签：function,allocation,about,returning,object,large,memory,data
来源： https://www.cnblogs.com/peabody/p/15350991.html

本站声明： 1. iCode9 技术分享网（下文简称本站）提供的所有内容，仅供技术学习、探讨和分享；
2. 关于本站的所有留言、评论、转载及引用，纯属内容发起人的个人观点，与本站观点和立场无关；
3. 关于本站的所有言论和文字，纯属内容发起人的个人观点，与本站观点和立场无关；
4. 本站文章均是网友提供，不完全保证技术分享内容的完整性、准确性、时效性、风险性和版权归属；如您发现该文章侵犯了您的权益，可联系我们第一时间进行删除；
5. 本站为非盈利性的个人网站，所有内容不会用来进行牟利，也不会利用任何形式的广告来间接获益，纯粹是为了广大技术爱好者提供技术内容和技术思想的分享性交流网站。