Date: 12/28/98
- Next message: Zeev Suraski: "Re: [PHP-DEV] CVS update: php3/functions"
- Previous message: Zeev Suraski: "[PHP-DEV] Re: [PHP3] Memory Issues"
- In reply to: Zeev Suraski: "Re: [PHP-DEV] CVS update: php3/functions"
- Next in thread: Zeev Suraski: "Re: [PHP-DEV] CVS update: php3/functions"
- Reply: Zeev Suraski: "Re: [PHP-DEV] CVS update: php3/functions"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, 28 Dec 1998, Zeev Suraski wrote:
> Ok, you did find a bug then, but the fix doesn't really fix anything.
If you consider a mem leak not to be a bug and a fix for such a bug not a
fix, then you are right.
> There's no reason to duplicate empty_string, ever, it can be returned as-is
> as it would never be freed by any part of the PHP engine.
Good to know. Besides that, you changed pg_fetch_row now, but didn't alter
pg_fetch_hash. Currently, pg_fetch_row has changed semantics and a
different behaviour in comparison to pg_fetch_hash.
Regards,
Sascha Schumann |
Consultant | finger sas <email protected>
| for PGP public key
-- PHP Development Mailing List http://www.php.net/ To unsubscribe send an empty message to php-dev-unsubscribe <email protected> For help: php-dev-help <email protected>
- Next message: Zeev Suraski: "Re: [PHP-DEV] CVS update: php3/functions"
- Previous message: Zeev Suraski: "[PHP-DEV] Re: [PHP3] Memory Issues"
- In reply to: Zeev Suraski: "Re: [PHP-DEV] CVS update: php3/functions"
- Next in thread: Zeev Suraski: "Re: [PHP-DEV] CVS update: php3/functions"
- Reply: Zeev Suraski: "Re: [PHP-DEV] CVS update: php3/functions"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

