This may be a little off topic, but I am sick of these "patterns," I am reading a book titled "Ajax Patterns" and honestly I never knew there were so many lame patterns.
Every time I read something on patterns I wonder this same thing, but have never been able to find an answer. :( Can someone please explain to me why something is deemed a pattern and not just implemented as a library? Or are patterns just a work-around for when your language lacks the necessary abstraction to express them as a library?(Actually, sometimes I see patterns that are too succinct and too trivial to bother with a library, but then I also wonder what's the point of codifying them as a pattern.)
I think that you can understand why patterns are so important by reading this : Quote: ".NET 2.0+ typed DataSet is a combination of Table Module, Unit of Work, Table Data Gateway and Metadata Mapping design patterns"From:<a class="user" href="http://aviadezra.blogspot.com/2008/06/patterns-for-enterprise-applications.html">http://aviadezra.blogspot.com/2008/06/patterns-for ...</a>When building enterprise application, "'Patterns of Enterprise Application Architecture'" provide vocabulary that is so powerful that your boss can explain it's idea to you in few sentences, instead of giving you a half hour lecture. The problem is that both you and your boss must know and understand the patterns...
addicted68098Sep 4, 2006
This may be a little off topic, but I am sick of these "patterns," I am reading a book titled "Ajax Patterns" and honestly I never knew there were so many lame patterns.
tybrisSep 4, 2006
Doesn't matter one bit, but obviously the second is vastly superior :P.
seventoesSep 4, 2006
I usually use the first one, the second looks ugly. I like my code to be neat.
surianSep 4, 2006
It makes no difference what your code STYLE is as long as your are consistent about it in your code. The two examples you listed are generally the ones used by programmers, however.It is usually helpful to look up the documentation about these formatting options for each of the languages you use. Sometimes it is beneficial to adhere to those standards while coding in that specific language (however it is usually not necessary).Try the following:<a class="user" href="http://java.sun.com/docs/codeconv/">http://java.sun.com/docs/codeconv/</a><a class="user" href="http://www.possibility.com/Cpp/CppCodingStandard.html">http://www.possibility.com/Cpp/CppCodingStandard.html</a>
ilitiritSep 4, 2006
edit: STUPID DIGG MISPLACING REPLIES >:(
feraldrinkerSep 4, 2006
Every time I read something on patterns I wonder this same thing, but have never been able to find an answer. :( Can someone please explain to me why something is deemed a pattern and not just implemented as a library? Or are patterns just a work-around for when your language lacks the necessary abstraction to express them as a library?(Actually, sometimes I see patterns that are too succinct and too trivial to bother with a library, but then I also wonder what's the point of codifying them as a pattern.)
biddessaApr 25, 2007
Ummm... I've always liked posts like that. Dugg.
aviadezJun 23, 2008
I think that you can understand why patterns are so important by reading this : Quote: ".NET 2.0+ typed DataSet is a combination of Table Module, Unit of Work, Table Data Gateway and Metadata Mapping design patterns"From:<a class="user" href="http://aviadezra.blogspot.com/2008/06/patterns-for-enterprise-applications.html">http://aviadezra.blogspot.com/2008/06/patterns-for ...</a>When building enterprise application, "'Patterns of Enterprise Application Architecture'" provide vocabulary that is so powerful that your boss can explain it's idea to you in few sentences, instead of giving you a half hour lecture. The problem is that both you and your boss must know and understand the patterns...