Iceberg76 wrote: Thank You You're welcome. Iceberg76 wrote: Do heap objects need to be called within functions, or can they be global as well? Pointers to heap objects can be global, or can be passed from routine to routine as needed. The objects themselves reside on the heap, which in a sense is a global data structure. Iceberg76 wrote: When should I use a heap object rather than using a global or stackobject? Using the heap is a good idea when you don't know how many objects you'll need. One time, you may only allocate one object. The next time, maybe you'll need ten. The heap lets you adapt to that kind of situation. Global objects have their good and bad points. They are good, in that a global object is easy to access from a lot of points in your software. Unfortunately, that's also their weak point. Since they can be accessed from everywhere, your software can get pretty tangled up. You'll find out that you can't change this feature of the object, because that part of the application depends on it. It can make maintenance and debugging a nightmare. Stack objects are useful when you know you only need the object for the duration of a given routine.
Software Zen: delete this;
