"Eddie Drapkin" <oorza...@gmail.com> wrote in message
news:68de37340905280737t3e1ad844y188ab8fa08f17...@mail.gmail.com...
> Your code might not, but you sure do! Spending all that time writing
> require statements = :(
If you are too lazy to write "require" statements then you are probably too
lazy to write readable, well structured and efficient code. Besides, I don't
use "require" statements, I use
$dbobject =& singleton::getInstance('classname');
I don't use autoload because *I* want to be in control. I prefer not to rely
on automatuic features which may not work as expected.
--
Tony Marston
http://www.tonymarston.net
http://www.radicore.org
> On Thu, May 28, 2009 at 9:49 AM, Tony Marston
> <t...@marston-home.demon.co.uk
>> wrote:
>
>>
>> <oorza...@gmail.com> wrote in message
>> news:000e0cd6ad1a9f7d3d046af89...@google.com...
>> > Two things:
>> >
>> > 1. Try using the fully qualified path (ie /var/www/foo/bar.php instead
>> > of
>> > foo/bar.php)
>> > 2. Look at setting up autoloading so you don't need to manually include
>> > anyway. If you're going OOP, autoloading is a must!
>>
>> I totally disagree. I have been doing OOP with PHP for years, and I have
>> never used autoloading. It is just a feature that can be used, misused or
>> abused just like any other. I choose not to use it, and my code does not
>> suffer in the least!
>>
>> --
>> Tony Marston
>> http://www.tonymarston.net
>> http://www.radicore.org
>>
>>
>>
>>
>> --
>> PHP General Mailing List (http://www.php.net/)
>> To unsubscribe, visit: http://www.php.net/unsub.php
>>
>>
>
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
