Home

	Expand Search

Sybase dbQueue Reference Guide

Chapter 1: Using the dbQueue Objects Library

Memory Management

Memory Management

The dbQueue objects library uses a "factory approach" to allocate and free memory:

• New instances are always created through methods instead of the C++ new operator. Methods that allocate new instances generally begin with the word New or List, such as NewAppDB().
• Instances are deallocated by calling Delete(), which is supported by every class in the dbQueue objects library. The C++ delete operator is not allowed.

The following sections summarize special memory management issues in the dbQueue objects library.

DbqEnv

DbqEnv is created by the static method DbqEnv::NewEnv(). All other classes are allocated by instance methods.

DbqEnv instances are deallocated using the Delete() method.

Lists

List methods always allocate a new DbqEnumerator instance. Client applications should call Delete() to eliminate the instance.

DbqEnumerator handles memory management for all instances it contains. Client applications should never deallocate instances in a DbqEnumerator list. Instead they must call Delete() only on the DbqEnumerator instance.

DbqErr

DbqErr instances are returned by FetchError(). Client applications must call Delete() to deallocate them.