While I'm still on my soapbox...
There are a number of great books out there on object oriented
programming. Basically the idea is to take a top down approach --
decide what components makes up what you want to do, what components
make up those components, and so on until you can program common
components together instead of having that much more code to modify.
And this is a /great/ way to tackle large projects. I have some
scripts where I use a 400 line function a dozen times. Much easier to
modify 400 lines when needed instead of 4800!
But at the same time, for quick and dirty projects it's not efficient.
If all you need is a quick 100 line script you'd be bloating your code
to use the OOP approach. The simple fact is that when you try to write
a function you have to create variables and other things to make it much
more general -- and that can be a lot harder then just /doing it/.
Plus, on a quick script it may become silly to break down things into
components unless you plan on expanding on the script at some point in
the future...
-Dan
On Wed, 2003-08-20 at 22:31, Chris W. Parker wrote:
> Dan and Ray,
>
> Thanks for your help. This helps clear some things up for me!
>
>
> Chris.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
