Re: memory leak (well, kind of...) ?

In <1spl0mINN67p@emory.mathcs.emory.edu> obelix.informix.com!johnl@emory.mathcs.emory.edu (Jonathan Leffler) writes: >Why on earth would a sane ESQL/C programmer use a function which is only >required to allow you to communicate with I4GL in an ESQL/C (and not I4GL) >program. Someone has seriously misread the manual (or misunderstood it), >to even think of doing that! How about when writing a library function which is designed to be called from ESQL/C or 4GL? (And no flames about whether that's good/bad/legitimate design or not, it's still a valid reason if you're the programmer and not the designer) graeme -- Disclaimer: The author's opinions are his own, and not necessarily those of Pyramid Technology Ltd. or Pyramid Technology Inc. --------------------------------------------------------------------------- -m------- Graeme Sargent Voice: +44 (0)252 373035 ---mmm----- Senior Database Consultant Fax : +44 (0)252 373135 -----mmmmm--- Pyramid Technology Ltd. Telex: Tell who??? -------mmmmmmm- Farnborough, Hants GU14 7PL Email: graeme@pyra.co.uk --------------------------------------------------------------------------- We have the technology. The tricky bit is learning how to use it.