Teach Yourself Borland C++ in 14 Days - portal

164 Day 5
Quiz
Q It seems like the component way of doing things is the best approach. Is that
true?
A It is true for many applications, but certainly not for all. In some cases a framework
such as OWL or MFC will be better suited to the task. For applications that use a
lot of dialog boxes and windows, and for database applications, VCL is probably a
very good choice. Overall, C++Builder is much easier to learn and easier to use
than the C++ class libraries.
Q Are properties just class data members?
A No. Properties are special creatures. Some properties simply set a data member in
the class. Other properties, when modified, invoke a method that performs special
operations with that property. In these cases, a property does more than just set a
data member.
Q Do I have to respond to each and every event a component defines?
A No. You can respond to as many events as is appropriate for your application, or
not respond to any events at all.
Q There sure are a lot of VCL classes. I thought programming with C++Builder
was going to be easy.
A Programming with C++Builder is much easier than programming Windows in C,
and easier than programming with a C++ framework like OWL or MFC. Windows
programming, no matter how good the programming tool, requires a lot of
experience and knowledge to master. Over time, you will master it if you keep at it.
Q Can I use C++Builder forms in my OWL and MFC programs?
A Yes. Later in the book I’ll show you how you can do that.
1. Are all components visible at design time and runtime?
2. Which is better—OWL, MFC, or VCL?
3. Can VCL objects be allocated locally (from the stack) as well as dynamically?
4. Are methods in VCL components equivalent to functions in C++?
5. Are all VCL classes ultimately derived from TObject?
6. Name one nonvisual VCL component.
7. Do all components share certain common properties?
8. Name two common properties that all visual components share.
9. Can two or more components share the same event-handling function?
10. What is the VCL terminology for a Windows device context? What is the name of
the VCL class that encapsulates device contexts?