I think one of the main forces behind design patterns is communication, they allow us to talk about software design using a common language which represents often found architectural features (errm, patterns :)
every programming language will have patterns, be it functional, OO, procedural, whatever. maybe some patterns (and anti-patterns) describe ways in which we deal with flaws (or features, depends on your point of view), but i think its slightly disingenuous to say that patterns are bandages for bad languages. (bad nicolas, bad.. :) i think they have been discussed a lot more in OO languages because most large scale software development has been conducted within that realm for the past so many years. Im sure we will start to see patterns relating to AOP in the near future as that becomes a more common part of development. anyway, back to the books, at the moment im also enjoying Refactoring: Improving the Design of Existing Code By Martin Fowler, Kent Beck, John Brant, William Opdyke, Don Roberts and joining the two topics together : Refactoring to Patterns By Joshua Kerievsky martin _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
