Chapter 14: Problem 6
In this chapter, we use the metaphor of a cookie cutter and cookies that are made from the cookie cutter to describe classes and objects. In this metaphor, are objects the cookie cutter, or the cookies?
Chapter 14: Problem 6
In this chapter, we use the metaphor of a cookie cutter and cookies that are made from the cookie cutter to describe classes and objects. In this metaphor, are objects the cookie cutter, or the cookies?
All the tools & learning materials you need for study success - in one app.
Get started for freeThe typical UML diagram for a class has three sections. What appears in these three sections?
You hear someone make the following comment: "A blueprint is a design for a house. A carpenter can use the blueprint to build the house. If the carpenter wishes, he or she can build several identical houses from the same blueprint." Think of this as a metaphor for classes and objects. Does the blueprint represent a class, or does it represent an object?
Look at the following pseudocode class definitions: Class Vegetable Public Module message() Display "I'm a vegetable." End Module End Class Class Potato Extends Vegetable Public Module message() Display "I'm a potato." End Module End Class Given these class definitions, what will the following pseudocode display? Declare Vegetable v Declare Potato p Set v = New Potato() Set p = New Potato() Call v.message() Call p.message()
What is a default constructor?
Why is an object's internal data usually hidden from outside code?
What do you think about this solution?
We value your feedback to improve our textbook solutions.