Re: another question on setting include paths for a project
| From: | Robert P. J. Day | Date: | Tue, 23 Mar 2010 16:39:22 +0000 |
| Subject: | Re: another question on setting include paths for a project | ||
| References: | 1 2 3 4 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-303145@lists.php.net to get a copy of this message | ||
On Tue, 23 Mar 2010, Richard Quadling wrote:
> However you want to identify the location, the autoloading techniques
> will allow you to only need to identify the location once. As compared
> to every file meticulously maintaining relative links to files.
>
> So, for testing, would this not work?
>
> RunTests C:\Dev\Checkouts\PROJ\trunk\tests
> RunTests C:\Installed\PROJ\V1.1\Tests
> RunTests C:\Installed\PROJ\V2.2\Tests
> RunTests C:\Installed\PROJ\V3.3\Tests
>
> sort of thing?
>
> And in RunTests, you set the location based upon the $argv[1] (using
> the autoloader technique).
>
> No env_var. No include_path.
sure, but deep down, you're still doing what i'm claiming has to be
done at some point -- *explicitly* identifying the target location.
you're just doing it in a different way, which is fine and might be
what i'm after.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================