Posted by Lars Eighner on 10/15/07 22:05

In our last episode, <1192482975.727615.56570@i13g2000prf.googlegroups.com>,
the lovely and talented duzhidian@gmail.com broadcast on comp.lang.php:

> If I move the programs to other places, using absolute paths will
> suffer, need to change every file.

Generally I use a project.ini where I use set_ini to modify the include path
for the project, then I never have to use paths in includes except for the
path to project.ini (possibly), but since it is a perl one-line to change
that (if necessary) I don't see the problem.

PS: why ./lib/b.php instead of lib/b.php ?


--
Lars Eighner <http://larseighner.com/> <http://myspace.com/larseighner>
Countdown: 462 days to go.
What do you do when you're debranded?

• Next in forum: Re: The principle of include files in PHP, not as in C++
• Prev in forum: Re: Regex help
• Thread view: Re: The principle of include files in PHP, not as in C++

[Reply to this message]