Re: [PHP] Best Practices for calling 'setup' classes that extend 'parent' classes?

2007-09-01 Thread Graham Anderson
Many thanks :) This was very helpful. On Aug 26, 2007, at 8:27 PM, Richard Lynch wrote: Put all your classes into a single directory structure. Use http://php.net/set_include_path (or php.ini or .htaccess) to provide the FULL PATH to that directory. PHP now knows where to start its search,

Re: [PHP] Best Practices for calling 'setup' classes that extend 'parent' classes?

2007-08-26 Thread Richard Lynch
Put all your classes into a single directory structure. Use http://php.net/set_include_path (or php.ini or .htaccess) to provide the FULL PATH to that directory. PHP now knows where to start its search, and essentially prepends that directory when it does an include. Assume this directory

RE: [PHP] Best Practices for calling 'setup' classes that extend 'parent' classes?

2007-08-20 Thread Jay Blanchard
[snip] What is the best practice for correctly targeting 'include' paths when using Initialization/Setup classes that extend Parent classes? In my extend_parent_class.php file, I have to provide an incorrect relative path. Apparently, the path (that does work) is relative to php file that