Re: Relativ Includes

Pierre-Alain Joye wrote:

On Thu, 31 Oct 2002 15:46:03 +0100 "Lukas Smith" <smith@dybnet.de> wrote:

(posted this to pear-general by mistake) Hi, well PEAR still has a serious problem imho with the issues we thought we could solve with dirname(__FILE__):

ssb response :-) : <ssb> There are two problems that need fixing here: being able to run tests from within a development tree, and using PEAR on systems where you can't modify include_path. We have to deal with these, but dirname(__FILE__) will cause more problems than it solves. Consider this a veto. :-) </ssb>

here i come again, with a response i also wrote as answer to Stig's veto! <again> but i think that is what is needed, if i have 2 PEAR installations with different versions of the files, i also just want tree one to depend on the files in tree one, not on the files in tree two. that's why i have 2 installations of PEAR. at least that's what i would need. example: imagine you have an old PEAR::someClass in tree one, which has an old API but in tree two the API of this class is the newest but since the application that works with the old API, so to say tree one is so huge, approved and stable that you dont want to or cant change the entire application, you need to have exactly this setup as dirname(__FILE__) would provide. i came across this problem a lot of times. and dirname(__FILE__) would solve it! or do i not understand something here? </again> -- Wolfram ... translating template engine .... http://sf.net/projects/simpletpl ... authentication system .... http://sf.net/projects/auth