>>This means that the string buffer has to stay around, until the parsing is
>>done.
>
>
> This is what the "t" signature char is doing anyway - Oops or better,
> what it should to. While it's using string_to_cstring the created string
> isn't freed (unless the library would free it, which is unlikely).
Actually it is freed right after the external function call. Which is bad when the freed memory is accessed later.
> > So what we need for the "t" signature is a string_pin with NUL append. Sounds good to me. I'm just wondering how string pinning can be tested. I guess I have to look into the garbage collection tests.
CU, Bernhard
-- ************************************************** Dipl.-Physiker Bernhard Schmalhofer Senior Developer Biomax Informatics AG Lochhamer Str. 11 82152 Martinsried, Germany Tel: +49 89 895574-839 Fax: +49 89 895574-825 eMail: [EMAIL PROTECTED] Website: www.biomax.com **************************************************
