Version 1.9 Build 803

News	FAQ
Search	Home

Up: NOTE 220 - AIPS++ SYSTEM PLAN Previous: Support of industry standards

Priorities for system

After the release in October 1999 two formal releases are foreseen until the end of 2000. The last release is meant to be used by any programmer who likes to develop code using AIPS++ classes.

Before the next release the following needs to be done:

Implement data proposal of Wim Brouw.
Improve using native exceptions. To prevent memory leaks, all variables on the heap should be put into an AutoPtr object until their pointer is taken over.
Split the library into some layered subpackages.
Build shared libraries from the lowest layers. Static variables sometimes cause problems, so we should try to get rid of them.
Improve the stability of the documentation system.
Improve cxx2html.
Have a better dependency analysis to link based on source code changes instead of library changes.

Before the following release:

Use threads in DO's to make them non-blocking. It requires that static data is thread-safe.
Port to Windows NT.
See if automatic template instantiation can be used. This is needed when heavily templated classes in Blitz++ or STL are going to be used.
Replace some of our classes by classes from the C++ Standard Library. Candidates are String, Complex, Map, Block. Other classes like valarray should also be looked at.
Use Blitz++ or techniques used in it to speed up the Array arithmetic.
Investigate how CORBA, DCOM, OLE, XML, ODMG, and Java can be used.

Up: NOTE 220 - AIPS++ SYSTEM PLAN Previous: Support of industry standards Contents