Differences

This shows you the differences between two versions of the page.

--- python:python_misc:oo_fundamentals_with_python [2018/08/23 17:07] – [Class-based object-orientation] mithat
+++ python:python_misc:oo_fundamentals_with_python [2018/11/30 18:28] – [Behavior] mithat
@@ Line 40: / Line 40: @@
 ==== Behavior ====
-A given microwave oven also has predefined **behavior**.
+A given microwave oven also has predefined **behavior**:
   * //Push the "1" button// → start cooking at maximum power for one minute.
-  * //Push the "+30sec" button// → add 30 seconds to the cooking time if it's already cooking or start cooking for 30 seconds at maximum power otherwise.
+  * //Push the "+30sec" button// → start cooking for 30 seconds at maximum power or add 30 seconds to the cooking time if it's already cooking.
   * //Push a magical combination of buttons// → set the internal clock.
   * And so on.
-These operations are ones that happen to be public-facing (i.e., operations a user can engage). There might very well also be operations that go on inside the oven to support the oven's functioning that the user will never be aware of. All these operations collectively define the oven's behavior. We call the public-facing behavior (i.e., the operations a user can engage) the oven's **interface**.
+These operations are ones that happen to be public-facing (i.e., operations a user can engage). There might very well also be operations that go on inside the oven that the user will never be aware of to support the oven's functioning. We call the //public-facing behavior// (i.e., the operations a user can engage) the oven's **interface**.
 ====  Encapsulation and protection ====
@@ Line 69: / Line 69: @@
 {{:python:about_python:farberware4241-200.jpeg?nolink|}}
-Because OOP models itself after real-world objects, we're going to use a real-world object to explore some more OOP concepts.
 I have a Farberware 4241 microwave oven in my office. It's small, but it gets the job done. There is a factory somewhere making these by the thousand million, and they make all the Farberware 4241s from a master plan. That master plan defines what the Farberware 4241 //is//. In computing terminology, we would call that master plan a **class**. A class contains all the specifications needed to make a particular kind of object.
@@ Line 269: / Line 267: @@
 ==== Next steps ====
-This just scratches the surface of what's possible with object-oriented programming. In particular, we haven't addressed the matter of protecting our class' members. But with even with the basics you have learned here, you can now create Python objects whose state is maintained through predefined behaviors.
+This just scratches the surface of what's possible with object-oriented programming. In particular, we haven't addressed the matter of protecting our class' members or reusing code through //inheritance//. But with even with the basics you have learned here, you can now create Python objects whose state is maintained through predefined behaviors.
 Copyright © 2011-2018 Mithat Konar. All rights reserved.