RE: [PEAR-DEV] include path solution?
| From: | Lukas Smith | Date: | Fri, 08 Nov 2002 08:28:21 +0000 |
| Subject: | RE: [PEAR-DEV] include path solution? | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-10609@lists.php.net to get a copy of this message | ||
> From: Stig S. Bakken [mailto:ssb@fast.no]
> Sent: Friday, November 08, 2002 8:06 AM
> To: Lukas Smith
> Cc: 'Stig S. Bakken'; pear-dev@lists.php.net
> Subject: RE: [PEAR-DEV] include path solution?
>
> On Thu, 2002-11-07 at 23:30, Lukas Smith wrote:
> > > From: Stig S. Bakken [mailto:ssb@fast.no]
> > > Sent: Thursday, November 07, 2002 10:59 PM
> > >
> > > The basic difference between using a constant and include_path is
that
> > > you can not change the constant, and using a constant adds a lot
of
> > > hassle while taking away lots of flexibility. I don't buy the
> > > performance argument, if you have exactly one directory in your
> > > include_path there is no difference.
> >
> > Hmm maybe I am missing something here .. but I want the constant to
be
> > user defined .. so where is the lack of flexibility? I doubt people
> > would be switching back and forth on their pear path in one script
call
> > ..?
>
> I'm not talking about switching back and forth, but rather adding
> another include directory at times. How would you give your script
the
> possibility of including from two include trees (for example your own,
> and the system-installed as fallback) using a constant?
>
so your solution also solves the issues with the test directory it
seems?
Regards,
Lukas