Miscellaneous and basic classes

Modules
	Functor objects
	Functors are used to encapsulate functions and member functions. There are a number of classes provided for different numbers of arguments. Functions and member functions are somewhat unified in that they both are goFunctorBase type objects, so e.g. for callbacks you can use either a function or a member function; they use the same interface. It is usually recommended to use the goFunction and goMemberFunction helper functions, which create goAutoPtr objects pointing to functor objects. To use a simple callback mechanism, you can utilise the goCaller classes, which provide an easy to use interface to connect to functors. If you then invoke a goCaller, all connected functors will be called.

Classes
class	goAutoPtr< T >
	"Smart pointer". Wrapper that automatically deletes its managed pointer when the internal reference count is zero and the last goAutoPtr is deleted. More...
class	goDate
	Simple date handling. More...
class	goException
	Exception base class. More...
class	goMemoryException
class	goFileIOException
class	goTypeException
class	goNullException
class	goMathException
class	goFileIO
	Reading/writing files and some utility functions. More...
class	goLog
	Logging facility. More...
class	goObjectBase
	Base class for golib objects. More...
class	goObjectMessage
	Message class for goObjectBase. More...
class	goObjectMethodParameters
	Parameter container for goObjectBase::callObjectMethod() More...
class	goStatusObject
	Provides status information for an object INCOMPLETE. More...

Enumerations
enum	goObjectMessageID {   GO_OBJECTMESSAGE_NONE = 0, GO_OBJECTMESSAGE_DESTRUCTING, GO_OBJECTMESSAGE_CHANGED, GO_OBJECTMESSAGE_NAME_CHANGED,   GO_OBJECTMESSAGE_USER = 0x0000FFFF }

Detailed Description

Introduction

This group contains miscellaneous and basic classes, like the goObjectBase class. This class provides for

• Generic method calls
• Inter-object "communication"
• Interfaces for writing and reading to and from files (this is not being used much but is indended to provide for a mechanism for storing and retrieving objects from secondary memory)
• Identification of classes by numeric IDs, objects by names. Class names exist through a hash table in goGlobal, that takes a numeric class ID as input and returns a goString.

goObjectBase

File Operations With goFileIO

Loading and Writing Images

goFileIO::readImage() and goFileIO::writeImage() can be used to read and write images to and from goSignal3D objects. This works only if the use of libdevil was enabled when golib was compiled (see building instructions). Naturally, golib can read and write any file format that can be read and written by the installed libdevil. There are also functions for reading and writing ASCII strings from and to files. See goFileIO for details.

Enumeration Type Documentation

goObjectMessageID

enum goObjectMessageID

Message IDs for goObjectBase object messages.

Enumerator
GO_OBJECTMESSAGE_NONE	Default message.
GO_OBJECTMESSAGE_DESTRUCTING	Sent when the destructor of an object is called (FIXME)
GO_OBJECTMESSAGE_NAME_CHANGED	Sent when an object changed its name (getObjectName()).
GO_OBJECTMESSAGE_USER	Start of message space to be used by applications using goLib and deriving from goObjectBase