Re: Re: cvs: php4 /pear DB.php /pear/DBcommon.phperror.phpmysql.php result.php warning.php
| From: | Stig S. Bakken | Date: | Tue, 05 Dec 2000 07:05:21 +0000 |
| Subject: | Re: Re: cvs: php4 /pear DB.php /pear/DBcommon.phperror.phpmysql.php result.php warning.php | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.pear |
| Request: | Send a blank email to php-pear+get-536@lists.php.net to get a copy of this message | ||
Chuck Hagenbuch wrote:
>
> Quoting "Stig S. Bakken" <ssb@fast.no>:
>
> > If the PEAR installation tool (the one called "pear") maintains an
> > autoload registry of functions/classes/macros and in which files they
> > are defined, the compiler could "require_once" all the necessary files
> > for you. No more "require_once" in PEAR or application code.
>
> You lost me a bit here. Are you talking about having PHP just knowing what
> files all of your classes live in, and loading them automatically? Sounds
> great, but tricky...
Yeah, that's what I'm saying. It would require two changes in PHP: the
autoloading itself, and a command-line option that can be used to print
tokens "class XXX" instead of executing the code. If the PEAR installer
uses this option, it's trivial to maintain a file with mappings between
class/function names and files.
- Stig