![]() |
Procedural vs oop programming
Which one you use and why?
|
Both but mostly procedural, because it's easier for clients to follow when they want to make minor changes themselves without actually knowing PHP.
|
95% oop for C#
|
Quote:
|
I write in Erlang and use functional one.
There's not much difference between OOP and procedure, both are imperative and both work with mutable data. |
Quote:
A language in itself is not OOP, its how you use it. A "modelling approach" so to speak |
Quote:
|
Quote:
|
I prefer oop (easier to maintain, easier to extend) in PHP. I however dont like the new style with namespaces and where evertyhing is a object (its really slow compared to classic oop/procedural).
|
It depends on the problem but clearly oop is the common choice.
|
I prefer poop programming over Procedural...
|
Quote:
|
Bump for more programmers
|
I've done lots of oops programming.
Oops, forgot the semicolon. Oops, forgot the bracket. Oops, gonna need an admin panel for that, aren't we. Oops, sorry I wiped out the database, but it's a whole lot cleaner now, don't you think. When I was in the military I was involved in one program where we went Oops, there goes the Chinese Embassy. I've been doing exclusively Oops programming since I started in on this shit and that is a long, long time ago. Figure I'll probably be doing Oops programming till the day I die. ;p . |
It depends on the size of the project imo.
If it's really small then procedural makes a lot of sense. It's quicker to code in most cases & as k0nr4d said easier for non-programmers to edit. However, as the scope & size of the project increases, you will find OOP to be much more efficient. Especially when you have multiple programmers working on the same code base. |
All times are GMT -7. The time now is 07:48 PM. |
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2025, vBulletin Solutions, Inc.
©2000-, AI Media Network Inc123