Re: Re: cvs: php-src / NEWS /ext/pgsql config.m4 config.w32 pgsql.c /ext/pgsql/tests 08escape.phpt 25async_query_params.phpt

From: Date: Wed, 30 Mar 2005 04:46:29 +0000
Subject: Re: Re: cvs: php-src / NEWS /ext/pgsql config.m4 config.w32 pgsql.c /ext/pgsql/tests 08escape.phpt 25async_query_params.phpt
References: 1 2 3 4 5  Groups: php.internals 
Request: Send a blank email to internals+get-15677@lists.php.net to get a copy of this message
If you really don't want to estrndup it for some reason, you are going to need to return a resource and manage that memory yourself through a set of access functions.
Well, it would be nice to be able to avoid having to strcpy large binary database objects... I guess I was thinking that there might be some sort of 'eacquire' function that can take an existing allocation and its length and "take over control of it"... Chris

« previous php.internals (#15677) next »