Sack Library Documentation
sack::app Namespace

Deadstart is support which differs per compiler, but allows applications access a C++ feature - static classes with constructors that initialize at loadtime, but, have the feature that you can create threads. Deadstart code is run after the DLL load lock under windows that prevents creation of threads; however, deadstart is run before main. Deadstart routines can have a priority. Certain features require others to be present always. This allows explicit control of priority unlink using classes with static constructors, which requires ordering of objects to provide linking order. Also provides a similar registration mechanism for atexit, but extending with priority. Deadstop registrations are done sometime during normal C atexit() handling, but may be triggered first by calling BAG_Exit

Registry offers support to register functions, and data under a hierarchy of names. Names are kept in a string cache, which applications can take benefit of. Strings will exist only a single time. This table could be saved, and a look-aside table for language translation purposes. Registry is the support that the latest PSI relies on for registering event callbacks for controls. The registry was always used, but, the access to it was encapsulated by DoRegisterControl registering the appropriate methods.

Application namespace. These are compiler-platform abstractions to provide a method of initialization that allows for creation of threads, and transparent (easy to use) method of scheduling routines for initialization. 
Contains methods dealing with registering routines and values in memory. Provisions are available to save the configuration state, but the best that can be offered here would be a translation tool for text strings. The namespace is savable, but most of the content of the registration space are short term pointers. Namespace containing registry namespace.
old notes - very discongruant probably should delete them.

Process name registry

it's a tree of names.
there are paths, and entries
paths are represented as class_name
PCLASSROOT is also a suitable class name
PCLASSROOT is defined as a valid CTEXTSTR.
there is... more 
Created with a commercial version of Doc-O-Matic. In order to make this message disappear you need to register this software. If you have problems registering this software please contact us at
Copyright (c) 2000+. All rights reserved.
What do you think about this topic? Send feedback!