Re: 4GL popquote mem leak workaround for Bug: 168224

superboer wrote: > Version: 7.20.UE2 on hpux... (YUK.. i know.) we should upgrade.. > will most likely happen someday... Are you sure an upgrade isn't easier than the workarounds? > ok: > > the application we use was written a long time ago and is putting > elephants on the stack where we pull them off using popint and > popquote to get the vars into > esqlc/c source. > > unfortunatly we are hitting a memory leak with popquote Bug: 168224 Don't have the bug database at hand... > When i look at straigt 4gl eq write a testprogram which does the same > it does not leak. > > eq call func() returning elephant.* > > when i use c4gl tessie.4gl -o tessie -keep it will give me the stuff > used. eq ld_quote , ld_long etc > > question: > is there a good reason why we should not use these as a temp > workaround. The theoretical reason is they're undocumented, so you don't know how to use them correctly. > (yes i do know that these f's change... 7.3 has > ibm_lib4gl_loadQuotedString > and ibm_lib4gl_loadint4 etc.) #include <fglsys.h> fixes most of the rename problems. It probably won't fix ld_quote() et al, and they get renamed! I still think you'd be better off upgrading! -- Jonathan Leffler #include <disclaimer.h> Email: jleffler@earthlink.net, jleffler@us.ibm.com Guardian of DBD::Informix v2003.04 -- http://dbi.perl.org/

> Are you sure an upgrade isn't easier than the workarounds? yes looking at the test traject for all the software. anywas thanks for your responce; we may have another w.a. which is pushing an int to c (which uniquely identifys an item ) and then prepare and describe the elepant and execute the prep'd elephant using the int. Anyways thanks for the responce. Superboer