"Eddie Drapkin" <oorza2k5@xxxxxxxxx> wrote in message news:68de37340905280801m6964d355l2d6d8ef773f3bc4f@xxxxxxxxxxxxxxxxx > There's a huge difference between laziness and opting in to use an > incredibly useful (and easy to properly deploy) feature to save myself > time > so that I can spend more time writing that structured and efficient code > of > which you speak. And the problem with what you're saying is that you > still > have to include 'singleton.php' somewhere in order to call its static > methods, I have a single general purpose include file which autmatically includes all other standard files, so I never have to explicity load my singleton class. > and I'd rather just spend 30 minutes writing an autoloader object > and letting it deal with finding any of the classes I use then trying to > keep track of legacy code I didn't write and require'ing them all over the > place. I'd rather not waste 30 minutes of my time writing a feature that I don't need. The difference between using and not using the autoload feature does not have any measurable impact on either my development times, nor the execution of my code, so I choose to not use it. That's my choice, and I'm sticking to it. > The way I look at it, if you spend all your time handling things that you > could automate - and if written properly, will always work as expected > (it's > called unit testing and debugging) - then you have no time to write that > structured and efficient code in order to meet your deadlines! :) Not using autoload does not have any noticeable effect on my deadlines, so I have no incentive to use it. Just because you say that I *should* use it carries no weight at all. -- Tony Marston http://www.tonymarston.net http://www.radicore.org > On Thu, May 28, 2009 at 10:53 AM, Tony Marston < > tony@xxxxxxxxxxxxxxxxxxxxxxxx> wrote: > >> "Eddie Drapkin" <oorza2k5@xxxxxxxxx> wrote in message >> news:68de37340905280737t3e1ad844y188ab8fa08f1705c@xxxxxxxxxxxxxxxxx >> > 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 >> > <tony@xxxxxxxxxxxxxxxxxxxxxxxx >> >> wrote: >> > >> >> >> >> <oorza2k5@xxxxxxxxx> wrote in message >> >> news:000e0cd6ad1a9f7d3d046af892f6@xxxxxxxxxxxxx >> >> > 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 >> >> > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
