design patterns reusable object oriented

After reading the story, I suddenly remembered the fable of the emperor's new clothes. 80% of the content in the whole book can be merged to the remaining 20%. Apart from some classic design patterns, there are too many far-fetched patterns, the example is not perfect, just as it is written for writing a book. I think it is only suitable for beginners of C ++ to

Today, I attended the course "C # object-oriented design patterns (1): Object-oriented Design Patterns and Principles. Summarized some notes

1. Concept of Design PatternsThe design pattern describes a general solution to some common problems in the software design process.2. Object-oriented design modeObject-oriented

Introduction to Design Patterns Each pattern describes a recurring problem around us, as well as the core of the solution to the problem.--Christopher Alexander The design pattern describes a general solution to a common problem in the software design process. Object-

JAVA8 Series Tutorials: Getting Started with JAVA8 programming, object-oriented programming, advanced programming, core design patterns--dao Design Patterns01_ "Introduction to JAVA8 Programming"02001_java Development ProfileInstallation and configuration of 02002_JDK02003_

return New F ();}He is an encapsulation of class inheritance, in fact, the transition object is equivalent to the subclass in the class inheritance, but in the prototype as a transitional object appears, in order to create to return the new instantiated object.Of course, if you feel the need to cache the F transition, you don't have to create a new transition class F each time, and then the Object.create (

, there is a problem that cannot be ignored:Explosive growth of subclass! ProblematicRoot Cause: Excessive use of inheritance to extend the object function, because inheritance is a type-introducedStaticSuch expansion lacks flexibility. How to solve the problem: static (compile-time) --> dynamic (runtime) Dynamically add some additional responsibilities to an object. In terms of functions, th

; 2. Decoupling customer code from complex object container structures is the core idea of the composite mode, the Customer Code will be dependent on the pure abstract interface, rather than the complex internal implementation structure of the object container, so as to better "respond to changes ". 3. In composite mode, "add, remove, and other methods related to ob