Re: [PHP4BETA] _very_ specific memory leak in Zend
| From: | chagenbu at wso dot williams dot edu | Date: | Sat, 15 Apr 2000 15:25:24 +0000 |
| Subject: | Re: [PHP4BETA] _very_ specific memory leak in Zend | ||
| References: | 1 | Groups: | php.version4 |
| Request: | Send a blank email to php-version4+get-13586@lists.php.net to get a copy of this message | ||
Quoting Andi Gutmans <andi@zend.com>:
> You should really be using require_once() (or include_once()) with the file
> extension.
Okay... test script:
<?php require_once './foo.php'; ?>done
produces this:
./zend-scanner.l(582) : Freeing 0x08140F1C (10 bytes),
script=/var/www/horde/imp/test.php
Doesn't seem to depend on length of the filename as far as I can tell.
So, is PEAR not going to be part of PHP4? I've been updating my classes to match
the conventions outlined in PEAR, and it seems like a very nice framework. But I
posted a question over a month ago about DB::factory() not working correctly,
and never heard anything about it - is anyone working on PEAR right now?
Also, I'd like to repeat the idea that include_path should by default include
the directory where PEAR classes are installed. This will make writing packages
that depend on PEAR _much_ easier for people to install. (someone else also had
the idea that the PEAR directory should be free of safe_mode restrictions, so
that hosts didn't have to give every single user a copy of the standard
packages).
-chuck