RE: include_path
| From: | Gavin Cowie | Date: | Sat, 23 Jun 2001 21:34:41 +0000 |
| Subject: | RE: include_path | ||
| References: | 1 | Groups: | php.smarty.general |
| Request: | Send a blank email to php-smarty-general+get-965@lists.php.net to get a copy of this message | ||
Hans wrote:
> I still think it's a bad idea that we
> need to alter the include path. Working on more
> then 10 projects (php related) would create an
> include_path longer then this email :( But then
> again, maybe I should just fix it myself and
> tell the users to only use the versions we distribute ....
The include path thingy is a first for me, I must say. But then this is the
first php templatey engine I've actually *wanted* to try.
(I had a little digression hear about Perl, Cpan, PHP and PEAR here, but
decided it didn't really further the discussion.)
I'm willing to say that template engines are of a sufficiently different
scope to other php projects that they have the "right" to require a runtime
change in the include path.
But Hans, does your "10 projects" comment imply having 10 projects using
Smarty means that you have to add an entry for each projects'
Smarty-template class into your php.ini?
I thought the ini_set command was only temporary, and if so, since you
already have to have a bunch of includes in your php just to use Smarty
anyway, is this a big deal?
I think I've just talked myself into a big knot, but hopefully some of this
is understandable ;)
G