Differences

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

--- python:python_misc:oo_fundamentals_with_python [2018/08/23 17:05] – [What you'll need to know] mithat
+++ python:python_misc:oo_fundamentals_with_python [2018/08/23 17:07] – [Class-based object-orientation] mithat
@@ Line 70: / Line 70: @@
 {{:python:about_python:farberware4241-200.jpeg?nolink|}}
-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. 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.
+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.
 Every Farberware 4241 begins its life identical to every other freshly-made Farberware 4241 because they were made using the same master plan. So, the one in my office that I pulled out of the box last month was identical to the one that I bought my best friend last week later because they were built from the same master plan, or, if you will, the same class. But as my best friend and I started using our ovens, the state of each changed. Note that while the behavior designed into the oven---the operations it's capable of---doesn't (and won't) change, the state of any individual oven does change over time.