Teach Yourself Borland C++ in 14 Days - portal

NOTE
NOTE
Creating Applications in C++Builder
OnClick handler associated with that button is still in the code. C++Builder knows that the
button associated with that OnClick handler is gone, but it still doesn’t delete the event
handler because it is possible that other components are using the same event handler. It’s
up to you to delete the event handler if you want it removed from your code.
The actual deletion of the event handler is an easy task:
■ Delete the function definition from the source unit.
■ Delete the function declaration from the header.
This is the exception to the rule that you should never modify the
published section of your form’s class declaration.
Before you delete the event handler, you need to make sure that no other components are
using that handler. Unfortunately, there is no simple way of determining whether another
component is using a particular event handler. You need to be aware of how the components
in your application interact.
Some might say that if you are unsure about an event handler being
used by other components, just leave it in the code. That’s a bad
solution, in my opinion. You need to take responsibility for knowing
what is in your code and getting rid of any unused functions. Although
unused code doesn’t hurt anything, it leads to a larger .exe file. In
some cases, unused code can lead to performance degradation. Be
diligent in paring your programs of unused or inefficient code.
Using Resource Files
Every Windows program uses resources.
Resources are the elements of a program that support the program but are not
executable code.
A typical Windows program’s resources include
NEW TERM
■ Accelerators
■ Bitmaps
■ Cursors
341
9