The great adaptability of C# is one of its assets, but coding for a wide variety of platforms can be overwhelming. This chapter by Steven John Metsker will help you adapt your code to different situations with ease. Also, Jim Mischel talks about the System.IO.Path class, which makes working with path names very easy. Also, learn how to use Visual Studio’s tools to throw and catch, elegantly and easily.
C# Design Patterns: Adapter
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
.. <a href=”http://c2.com/cgi/wiki?AreDesignPatternsMissingLanguageFeatures“>… is my point of view, usually.
I guess adapter is needed whenever you don’t have a generalized type derivation system.
But this was a nice article, anyway.
Design patterns usually underscore the lack of fully general macros in a language. As Alexanderscu points out in “Modern C++”, and as Lisp programmers have known for awhile, metaprogramming allow design patterns to be packaged up into a concrete language construct, without including it in the base language. There is an intersting article by Peter Norvig about how many of the classic design patterns can be specified concretely in languages like Lisp and Dylan:
http://www.norvig.com/design-patterns/ppframe.htm
actually your link is linked from the page I linked
And this has what to do with C# Adapter Design Pattern?
maybe it means that you should Adapt to the java Design and politics or follow MS in the usual embrace and extend Pattern?