I want to make a few words about this article before the topic. I recently read a lot of articles about OO, most of the feeling of people is still too theoretical, too poor, and very formified. When I wrote this article, I noticed this problem, it is best not to take it too theoretical. It is mainly to say that I have some understanding and opinion of OO.
I think I have a good C learning Java naturally has OO thinking.
Can I design a high quality OO model with some grammar?
It is considered that the process has been eliminated. It must have a higher quality using OO.
Is Oo really a doctor, is there any invincible in the world?
Considering the project always starts from the interface, repeatedly out the view on the paper.
Is this also calculated using OO to analyze and design?
It's all the UML in your hand, written is a pile of Class, which is one by one Pattern.
It is rare that this is to think with an OO perspective?
Get the code of others C, first despise, and then put those global functions, global variables into a class.
Is this what we need?
I feel that I am cow, I don't believe in the code written by other comrades, let alone those DLLs, I always feel that the black box is not very.
Is this the spirit of OO needs?
Too much is it to make me lose, but it doesn't matter, it seems that people around them are like this. I am afraid of who ?!
You have to say that you haven't OO, you are embarrassed to talk to people, how do you mix it in the forum ?!
We are all looked elsewhere with Class, DeriVation, Hierarchies, UML, Java, Case. But we don't know why you want to use it? When you are, even if you don't know what to write, most people will shout with the flag. Many comrades write code, they also have the old books of the year. What is C , what is oo? Isn't a number of Class, DeriVation, Hierarchies just get two grammar books, it will be very clear. However, we are also in the form of a form.
We are all looked elsewhere with Class, DeriVation, Hierarchies, UML, Java, Case. But we don't know why you want to use it? When you are, even if you don't know what to write, most people will shout with the flag. Many comrades write code, they also have the old books of the year. What is C , what is oo? Isn't a number of Class, DeriVation, Hierarchies just get two grammar books, it will be very clear. However, we are also in the form of a form.
Sometimes I feel that from c to c too much. On the one hand, the purpose of is of course to facilitate comrades to smoothly transition from C to C , and the convenience of C and OO. On the other hand, has indeed harmed a lot of people. To know that C is in the process ideas and OO thinking in C , it is two distinct thinking patterns. So this is also a thorough misleading. At least I was deceived. One lie is three years.
In the object-Oriented Thought Process, the author also expresses his point of view on this question. Let's take a look at http://blog.9cbs.net/nonocast/archive/2005/03/27/332198.aspx.
Many people are there to learn OOA, OOD, OOP, UML, and various Cases.
Said in The Oo Design Process:
First, at its core, object orientation is not at all about derivation, class hierarchies, UML, Java technology, and so forth. These are tools that the OO designer puts to use in order to structure the analysis, the design, and the implementation , but the aren't center to what makes an oo program object-oriented.
See http://blog.9cbs.net/nonocast/archive/2005/04/06/338231.aspx See us before, such as Class, DeriVation, Hierarchies, UML, and Case are helping designers to complete OO design Tools (Tools). The equipment is just the embodiment of the ideology and extension, so before learning tools and patterns, we need to master the way OO thinking, OO thinking!
After several OO and non-OO, I started to seriously reflect on this series of questions. From my perspective, most of them are handsome. Fortunately, I still have some time calm and think about what is true oo.
About OO specific issues I will discuss in the next chapter. Said so much nonsense, actually only wants two questions, and finally summarizes:
1. Why should I write this article?
I started to write this article or it is still very simple, because this person does not have long memory, time is long, easy to forget. During the entire process of studying OO, it is constantly prepunied, constantly negative, continuous pushback, and after the arrogance after the month, after the moment of the moment, go back and see everything is so that 'rational'. It may be said that there is only two two sentences, but who will care about the process before this before? Master seems to be deliberately avoiding your own 彷徨, replaced by the direct and comrades of the results after they understand, Comrades will follow the master Step by step. Compared to those models and rules, I care more about the process of thinking.
Later, I found that many comrades were free to be between Oo and Non OO as before, so I hope to share my little experience with them. The content of the article does not dare to be completely correct, but it is my experience in this time, using this opportunity to write it out, and communicate with you. As long as I dare to say this article, you feel that there are three words in the middle of this article very useful. I personally feel very pleased. So many masters have conducted an in-depth study of OO, and I am particularly struggling to discuss this problem in this place, and write such an article is a very rare thing. I hope that our purpose is to think about some thinking, some inspiration. This thing brings us some reflections.
2. This article deserves you to take time?
At present, there are a large number of books in Oo, UML, Design Patterns on the market, including excellent works, can refer to http://blog.9cbs.net/nonocast/archive/2005/04/05/337536.aspx.
Almost all books are telling us how Oo is superior, how to use OO to analyze design, how to use various patterns, how to draw UML maps, and provide a wide variety of Study Case. And I want to focus on how to form the correct OO thinking, how to look at OO and solve the problem.
Everything can only be shallow only, in order to be self-contained in your chest. Thank Jjhou's deep-in-depth MFC. This book not only analyzes the MFC internal mechanism, but also the method of teaching me, this method is much more important than a certain technology.
