Re: [PHP] everything as classes

2008-04-05 Thread Larry Garfield
On Thursday 03 April 2008, robert wrote: > Along the lines of a previous post "How to get a code review", I am > curious if it is overkill to create everything in classes. For > example, a movie website where there is a class for the movie > datatype, class for getting/adding/deleting/updating movi

Re: [PHP] everything as classes

2008-04-04 Thread robert
Hi After spending yesterday afternoon I cleaned up my code and simplified in many places. I really like the idea to use Static class for "single use" database operations. Thank you very much to you that responded with comments. -robert On Apr 3, 2008, at 11:23 AM, Richard Heyes wrote: Al

Re: [PHP] everything as classes

2008-04-03 Thread Richard Heyes
Along the lines of a previous post "How to get a code review", I am curious if it is overkill to create everything in classes. Everything, yes. Sometimes all you need is a quick and not so dirty function. Though saying that, OO is generally thought of as the way to go. > For example, a movie

Re: [PHP] everything as classes

2008-04-03 Thread Nathan Nobbe
On Thu, Apr 3, 2008 at 10:33 AM, robert <[EMAIL PROTECTED]> wrote: > Along the lines of a previous post "How to get a code review", I am > curious if it is overkill to create everything in classes. For example, a > movie website where there is a class for the movie datatype, class for > getting/ad

[PHP] everything as classes

2008-04-03 Thread robert
Along the lines of a previous post "How to get a code review", I am curious if it is overkill to create everything in classes. For example, a movie website where there is a class for the movie datatype, class for getting/adding/deleting/updating movie's data to the database, and class for d