Re: Re: When to use design patterns?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Saturday 23 February 2008, carlos wrote:
> skylark wrote:
> > Design patterns are really hot today.
> > And I am really interested when and how often they are used.
> >
> > It is said that 99% of the projects don't need them.
>
> Design patterns are used to solve common problems to in OOP programming.
>
> If you use OOP, chances are you have used a design pattern without even
> being aware of it.

Untrue.  Design patterns are not OOP-specific, although they are frequently 
discussed in OOP terms.  

Design patterns are just that: A formalization of various common patterns that 
come up over and over in programming.  Ever get the feeling "wow, I know I've 
written something kinda like this at least three times now?"  That means it's 
probably a design pattern of some kind.

Studying design patterns helps you recognize a give problem as being similar 
to another, so the solution is probably similar.  It also can alert you to 
common pitfalls and common ways around them.  

-- 
Larry Garfield			AIM: LOLG42
larry@xxxxxxxxxxxxxxxx		ICQ: 6817012

"If nature has made any one thing less susceptible than all others of 
exclusive property, it is the action of the thinking power called an idea, 
which an individual may exclusively possess as long as he keeps it to 
himself; but the moment it is divulged, it forces itself into the possession 
of every one, and the receiver cannot dispossess himself of it."  -- Thomas 
Jefferson

-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php


[Index of Archives]     [PHP Home]     [Apache Users]     [PHP on Windows]     [Kernel Newbies]     [PHP Install]     [PHP Classes]     [Pear]     [Postgresql]     [Postgresql PHP]     [PHP on Windows]     [PHP Database Programming]     [PHP SOAP]

  Powered by Linux