Jul-31-2020, 06:18 PM
(This post was last modified: Jul-31-2020, 06:18 PM by deanhystad.)
OOP has become a catchphrase that many equate with "structured programming". If you code is organized well and easy to use it must be OOP, right? This is completely wrong of course.
The attitude that OOP is good and all else is bad has lead to a backlash against OOP and interesting articles asking if OOP is a good choice for any problem space.
I don't seeing a password database as a good fit for OOP. The only "object" is the database, and that object is modeled by the database API. I suppose if you really dislike the mysql API you could make an object oriented wrapper.
Is this an assignment where you have to use classes to solve the problem?
The attitude that OOP is good and all else is bad has lead to a backlash against OOP and interesting articles asking if OOP is a good choice for any problem space.
I don't seeing a password database as a good fit for OOP. The only "object" is the database, and that object is modeled by the database API. I suppose if you really dislike the mysql API you could make an object oriented wrapper.
Is this an assignment where you have to use classes to solve the problem?