Do you use Object Oriented PHP?

[moon 111]

I've been curious about the percentile for a while. I use OOP.

[Stooney]

hard to live without it

[fert]

In general no.  The only time i use OOP is to demonstrate that i know it.

[Daniel0]

I hardly ever use anything else other than for really small scripts or code examples.

[unsider]

I hardly ever use anything else other than for really small scripts or code examples.

 

 

[charliepage]

Nope, but I would like to.

[zq29]

I almost always write my code procedurally - I have a basic understanding of OOP, in the way that I can use and modify classes that others have written (PHPMailer, jpGraph, FCKEditor etc.) But as far as writing and utilising my own, I have never attempted it. I have a book on OOP but have only read the first chapter or so - I just can't think of a situation where it would benefit me. Though, maybe my opinion would change if I had a better understanding of the subject.

[neylitalo]

When I write simple test scripts, it's really a waste of time, but with any respectable project, there's no other way to do it.

 

SA: If you do it properly, it's very easy to implement a system that will save you a lot of time in development. Put the right directories in include_path, put the right code in the right directories, and fill in the __autoload function, and then all you have to do is make the new classname() call. __autoload takes care of the include or require call, and voila, you have your classes.

[zq29]

SA: If you do it properly, it's very easy to implement a system that will save you a lot of time in development. Put the right directories in include_path, put the right code in the right directories, and fill in the __autoload function, and then all you have to do is make the new classname() call. __autoload takes care of the include or require call, and voila, you have your classes.

Hmmm, I have often wondered if OOP would speed up the development of my 'back-end' administration areas for projects, as they are almost always based on the same layout and similar functionality (create/modify/remove content fields) - I always start a new project by copying the contents of the previous project and modifying it to fit the requirements of the new one, improving things along the way if I can and writing new functionality if required.

 

I have "PHP 5 Objects, Patterns, and Practice" (APress), I bought it after a recommendation by someone on here. Although what I have read makes sense, it just doesn't outline the clear benefits for going OOP. I'd like an article that shows the same practical functionality coded in both procedural and OOP methods where the gains are obvious. I've yet to find one, does anyone know of such an article (or book)?

[sKunKbad]

Having an understanding of OOP, and php5's built in classes, is essential in my opinion. Also, there are so many free classes floating around out there, that not knowing how to use them is a real disadvantage to a beginner.

[LemonInflux]

I generally tend to avoid it, usually because I can't see why using classes is any quicker than a function library. There probably is a reason, and I'd love to know it, but right now I don't see anything wrong with functions.

[some1]

 

I hate to edit other people classes..

[Daniel0]

I generally tend to avoid it, usually because I can't see why using classes is any quicker than a function library. There probably is a reason, and I'd love to know it, but right now I don't see anything wrong with functions.

 

There is much more to OOP than just using objects/classes. It's not comparable to using a function library.

[shlumph]

 

I hate to edit other people classes..

 

I hate to edit other peoples procedural junk 

 

 

[Bladescope]

Ever since I found out about them, i've never been able to script without them.

[mejpark]

I learned the theory behind object-oriented programming at uni (Java), and scored fairly well.  But knowing is one thing - doing is another!  I definately want to learn OO-PHP though, but not until I reasonable comfortable with procedural PHP programming.