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!
On May 28, 2009 8:49am, kranthi kranthi...@gmail.com wrote:
i
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,
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
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
Eddie Drapkin oorza...@gmail.com wrote in message
news:68de37340905280801m6964d355l2d6d8ef773f3b...@mail.gmail.com...
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
5 matches
Mail list logo
