On 14 May 2010 15:31, Michael N. Madsen <m...@criion.net> wrote:
> Since php started to support oop it has moved more and more features in that
> direction.
> This is good for me because I love oop. Then came _autoload() and I was
> rejoiced only to find that this (no fun)ction can't be used to it's fullest
> potential in oop unless I have all the files in the same directory. This is
> where you correct me and tell me how I can have a file structure in more
> then one level and still get the ripe juices of _autoload() (Please, I beg
> you!)
> I have looked at the comments on the doc page of the function and every
> single one comes with the addition of many, often complex lines of code that
> will only add more load on the server. If _autoload can't figure out the
> correct path to the file which defines the class, then what is the point
> from an oop pov?

__autoload() is triggered when a class referenced isn't already
loaded. It gives you the chance to load the class by requiring the
needed file - but there's no way PHP has any idea of how many files
you have in your project, so YOU have to tell PHP which file to load.
 This, to most people, means coming up with a meaningful way of naming
files and classes so you can parse the class name and then know where
to grab the file from (Zend naming for instance:
Zend_Db_Table_Abstract gets parsed to Zend/Db/Table/Abstract.php). So
no, you don't have to stress the server a lot - but you do have to do
some manual work.


WWW: http://plphp.dk / http://plind.dk
LinkedIn: http://www.linkedin.com/in/plind
Flickr: http://www.flickr.com/photos/fake51
BeWelcome: Fake51
Couchsurfing: Fake51

PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to