I don t know much about what exactly is the concept of object orientation40

It can be understood like this:

Process-oriented means that you need to know how to do the whole process. Object-oriented, on the other hand, means that you only need the method that the other party provides you with how to do it, and you only need to call it.

I'll give you an example. If you need to entrust someone to buy you a bottle of soda, using a process-oriented approach, you have to explain to this person: yours go downstairs first, then go out and turn left, go to the commissary, talk to the owner to ask for a soda, pay for it, get it back, and give it to me.

And if you use an object-oriented approach, the person provides a "buy soda" method, and you just have to tell the person: buy me a bottle of soda. You don't need to care about the person's soda buying process, you just need to pay attention to the result of his "soda purchase" is to give you a bottle of soda.

Although you may still need to design this "buy soda" method, from the programming idea, as long as you define this "buy soda", you can just focus on what method is called when and when you don't need to pay attention to its process.

That's the difference between process-oriented and object-oriented, I don't know if my explanation is clear, hehe.

There is something wrong with your understanding.

For example, in the case of boxes, object-oriented is to put boxes"Such objects"As one"class", adding open and close methods, functions, and wide and high properties to this box class.

Specific to the box you operate--- that is, the box you open and close, is to create a box object based on this box class.

At this point, you can manipulate the box object.

If you have 100 boxes, you can construct 100 objects, and you don't have to write the properties and functions yourself, isn't it convenient?

But if you have a box and it is locked, then the method of opening it will change, and you need to unlock it first.

What to do? To derive a locked box class from the box class, and then overload the open method.

It's that simple.

If you still don't understand, I'll give you an easy way.

What can be expressed in terms of quantity is the object, and vice versa.

Flower and a flower are classes and the latter are objects.

Let me briefly use an example of object orientation.

The concept of a human being is a class.

The concept of a person is an object.

People have something in common. For example, nose, eyes. This is the field, the property.

People have common behaviors. For example, eating, sleeping, making love (to be harmonious). It's the method, the event.

human oneperson = new human()；

A "person" is generated from the "person" class.

This person is the object.

All you need to do is do this object.

For example, onepersonEat ().

Object-orientation isn't that simple, but you can start here.

Practice more. Don't look at design patterns. If you don't know what object-orientation is. You're going to get dizzy.

There is a big difference between process orientation and object orientation, and you only have a small part of your understanding of it now, and you don't know the benefits of object orientation when you're working on a project with a lot of content.

It's hard to say that object-orientation is a thing, and you can only understand it on your own. Don't compare procedural orientation and object orientation to two different concepts. The more you use it in the future, you will understand it.

It is encapsulable, scalable, reusable, and flexible.

It can be encapsulated, the ** is encapsulated, it can be reused, and the previously encapsulated ** can also be used elsewhere.

Extensible, leaving an interface so that the program can be changed in the future, and the changed part can be expanded according to the interface.

Design patterns: These books are too early for you to read them, and they can only be misleading.

oo these thoughts, including its characteristics, you can only understand it by writing more ** and comprehending it, I believe that everyone has their own set of ways to understand oo, so these things have to be understood by yourself. Hey.

**Write more to know the difference here.

Without actual development experience, it's hard to imagine the difference between object-oriented and process-oriented.

If you look at the book on design patterns, the idea of object-oriented programming is not easy to establish.

Let's figure out the object-oriented thinking first, and then figure out the design pattern, and I want to run before I know how to go.

1. Object-oriented is a software development method, a programming paradigm. The concept and application of object-oriented has gone beyond programming and software development to include database systems, interactive interfaces, application structures, application platforms, distributed systems, network management structures, CAD technology, artificial intelligence, and other fields. Object-oriented is a method of understanding and abstracting the real world, which is a product of the development of computer programming technology to a certain stage.

2. Object-oriented is relative to process-oriented, object-oriented approach, which organizes relevant data and methods as a whole, and conducts system modeling from a higher level, which is closer to the natural operation mode of things.

The use of object orientation is very important in programming languages, and it took many years to acquire this technology in PHP languages. The advent of object-orientation was a great revolution in system development, and programming languages began to move from applications back to data. Object-oriented brings applications closer to the real world by shifting the focus of the programming process to the real thing being modeled.

The following computer training mainly introduces object-oriented for you.

1. What is object-orientation?

It's like you're the president of a company, and you're doing the job of assembling a set of computers. In other words, object-oriented is either an abstract execution or a scramble done by the employee. In detail, the president is not required to think about this issue.

IT training believes that the benefits are obvious, that high-level management companies can coordinate work without managing high-level companies, and that only a few employees who are specifically implementing will be stuck.

2. Object-oriented characteristics.

1. Encapsulation. Hides the properties and implementation details of objects, exposes only the interface to the outside, and controls the access level of reading and modifying properties in the program; Combine abstract data and behaviors (or functions) into an organic whole, that is, organically combine data with the source of operating data to form a "class", where data and functions are members of the class.

2. Inheritance. Inheritance is the mechanism by which one or more classes are derived from a base class. A class that inherits from another class is called a subclass of that class.

This relationship is often compared to that of a father and a child. A child class inherits the properties of the parent class. These properties consist of properties and methods.

The North Jade Bird believes that the subclass can add new functions other than the parent class, so the subclass is also called the "" of the parent class.

3. Polymorphism. Polymorphism refers to the fact that OOP can redefine the nature or behavior of a class depending on the context in which it is used, or that many different implementations of an interface are polymorphic. Beijing Beida Jade Bird suggested that if the child object that does not mess with the basis is regarded as the parent class, the differences between different child objects can be shielded, the general ** can be written, and the general programming can be carried out to adapt to the change of requirements.