Frank Buss <[EMAIL PROTECTED]> writes: > Surendra Singhi wrote: > >> Can I use the above snipped text in some wxCL documentation? > > Yes.
Thanks. >But if you want to use the code, you should fix the wxCL library, > first, if not already done in the latest release: The number of returned > chars (e.g. text control getValue) must not depend on the size of the > buffer (and a memcpy must not copy beyond, if you really want to use this > technique). If a wxString is returned, it should be limited by memory, > only, and with no memory leaks, if possible. > Yes, this style of returning strings has been changed. In most of the places the new release returns a malloced C-string which is declared as `:malloc-free' so that c-lisp can garbage collect (or free it) when no-longer in use. This doesn't causes any memory leaks as the reference variable is not being copied. -- Surendra Singhi http://www.public.asu.edu/~sksinghi/index.html ,---- | WHY SHOULD WE SAVE TIGER? | Ans: Saving the tiger means saving mankind.. | | Help http://pudang.tripod.com/ | or https://secure.worldwildlife.org/forms/tiger_appeal_1.cfm `---- _______________________________________________ Gardeners mailing list [email protected] http://www.lispniks.com/mailman/listinfo/gardeners
