On 23 March 2010 16:39, Robert P. J. Day rpj...@crashcourse.ca wrote:
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
On Mon, 22 Mar 2010, Nilesh Govindarajan wrote:
What I do is, set the include path in the top-level bootstrapper.
/bootstrap.php:
set_include_path(dirname(__FILE__) . '/lib' . PATH_SEPARATOR .
get_include_path());
Then I load the autoloader from /lib/autoload.php at the time of bootstrap.
On 23 March 2010 13:11, Robert P. J. Day rpj...@crashcourse.ca wrote:
On Mon, 22 Mar 2010, Nilesh Govindarajan wrote:
What I do is, set the include path in the top-level bootstrapper.
/bootstrap.php:
set_include_path(dirname(__FILE__) . '/lib' . PATH_SEPARATOR .
get_include_path());
Then
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?
to recap regarding an earlier question i asked regarding extending
include paths, i have an existing project (call it proj currently
all under a top-level directory also named proj) which can be SVN
checked out anywhere under a user's home directory. so in my case, i
might have my svn working
On 22 March 2010 14:18, Robert P. J. Day rpj...@crashcourse.ca wrote:
to recap regarding an earlier question i asked regarding extending
include paths, i have an existing project (call it proj currently
all under a top-level directory also named proj) which can be SVN
checked out anywhere
On Mon, 22 Mar 2010, Richard Quadling wrote:
Depending upon what is being included, an autoloader could help
here.
The main payoffs for autoloading are reduced memory footprint (class
are loaded JIT) and no need for each class to know exactly where the
other classes are.
So, your main
On 03/22/2010 07:48 PM, Robert P. J. Day wrote:
to recap regarding an earlier question i asked regarding extending
include paths, i have an existing project (call it proj currently
all under a top-level directory also named proj) which can be SVN
checked out anywhere under a user's home
On Mon, Mar 22, 2010 at 10:51:38AM -0400, Robert P. J. Day wrote:
On Mon, 22 Mar 2010, Richard Quadling wrote:
Depending upon what is being included, an autoloader could help
here.
The main payoffs for autoloading are reduced memory footprint (class
are loaded JIT) and no need for
On 3/22/10 10:25 AM, Paul M Foster wrote:
That's the key. You can do anything you want inside __autoload(). If you
must consult something in the environment, there are a couple of ways to
do it. First, set a variable in the $_SESSION array, and consult it in
__autoload(). Second, use a
On 22 March 2010 15:28, la...@garfieldtech.com la...@garfieldtech.com wrote:
On 3/22/10 10:25 AM, Paul M Foster wrote:
That's the key. You can do anything you want inside __autoload(). If you
must consult something in the environment, there are a couple of ways to
do it. First, set a variable
On 22 March 2010 14:51, Robert P. J. Day rpj...@crashcourse.ca wrote:
On Mon, 22 Mar 2010, Richard Quadling wrote:
Depending upon what is being included, an autoloader could help
here.
The main payoffs for autoloading are reduced memory footprint (class
are loaded JIT) and no need for each
oops, mailed the OP direct rather than the list. sorry.
Originele bericht
Onderwerp: Re: [PHP] another question on setting include paths for a project
Datum: Mon, 22 Mar 2010 15:58:28 +
Van: Jochem Maas joc...@iamjochem.com
Aan: Robert P. J. Day rpj...@crashcourse.ca
Op 3
13 matches
Mail list logo
