× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Brad,

The malloc() function will always allocate in single-level store, likewise _C_TS_Malloc() will always allocate in teraspace. It does not matter which storage model you compile your RPG with. You do not need to compile with the teraspace storage model to use teraspace allocations from _C_TS_malloc().

If you were coding in C, there is a preprocessor directive that will map malloc() to _C_TS_malloc() automatically if you specify teraspace. But, that's not the case in RPG.

I believe that if you use a teraspace storage model that the RPG %alloc/dealloc will use teraspace as well. But, then your whole program model is teraspace which can cause issues with callers also having to be teraspace. Since I only needed teraspace memory for things that I specifically allocate, there wasn't any need for that in yAJL.

-SK



On 6/6/2017 2:07 PM, Bradley Stone wrote:
I am just curious if there is much or any difference in using
_C_TS_free() or free vs the dealloc RPG opcode.

I was looking through Scotts YAJL parser setting it up for teraspace
and noticed Scott used _C_TS_malloc64() or malloc() (depending on if
TS is being used) and frees that space using the RPG opcode dealloc
instead of _C_TS_free() or free().

It wouldn't appear to be much difference, but I'm sure there is.

Thanks!

Bradley V. Stone
www.bvstools.com
Native IBM i e-Mail solutions for Microsoft Office 365, Gmail, or any
Cloud Provider!


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

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.