Instead of defining objects at compile time, objects are created at run time by calls to routines from either C or FORTRAN. The system also has tools to generate header files if desired. There is an object description language which can describe the data objects in an external file (much like .ZEB files). A C++ binding is in pre-release which supports mapping into inheriting classes.
The data structures know names (in memory, and on tape), and contents may be fetch by whole structures (which can be read into structures defined in the calling language if you desire), or fetched piece by piece, by name. Complex structures can be built of lower level structures.
The details of the memory manager are hidden from the user (no more IQ(L+17)).
Instead of pointers (links) one uses "handles", an id number generated by THE SYSTEM and returned to the user. You are not responsible for the validity of the link; your only obligation is to not change the handle. The effect is as if all links to objects are in link areas. There is a mechanism for writing out and preserving user pointers among data structures.
It can use ZEBRA FZ for I/O. It may use ZEBRA underneath for memory management, but you basically can't see that. A version is being developed with a different memory manager.
There are plans for an automated system of tracking versions of data objects as they evolve.
From: Predrag Buncic <buncic@cern.ch> Cc: Ryszard Zybert <zybert@np.ph.bham.ac.uk> Subject: Re: files for DSPACK manuals Unfortunately, the manuals are not kept 100% in sync with developments but you'll get an idea what is going on... If you have an access to AFS, you can find all sources and binaries for HP-UX and AIX in directory /afs/cern.ch/na49/library/March95/DSPACK The code will also compile on Sun (Solaris) and SGI (IRIX). You can also fetch DSAPCK tar file using anonymous ftp from ~/pub/DSPACK directory on hpna49-1.cern.ch. If it happens that you port it to another platform or if you have some questions or problems, you can ask me or Ryszard Zybert <zybert@np.ph.bham.ac.uk> who is the author of DSPACK code.... You can also search with the keyword DSPACK in abstract the index of NA49 documents . Regards, Predrag
Jim Linnemann