Getting Started Documentation Glish Learn More Programming Contact Us
Version 1.9 Build 803
News FAQ
Search Home


next up previous contents
Next: Other work (Tim Cornwell) Up: System (Ger van Diepen) 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 (1.3) the following needs to be done:

  1. Makedefs reconcilation High GVD 1w
  2. Implement data proposal of Wim Brouw High WB 2w
  3. Automatic tools for patch generation. e.g. Have a better dependency analysis to link based on source code changes instead of library changes High GVD 2w
  4. Investigate ways and advantages of partitioning libraries. Medium GVD 2d
  5. 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. Low GVD 4w

Before the following release (1.4):

  1. Use threads in DO's to make them non-blocking. It requires that static data is thread-safe.
  2. Port to Windows NT.
  3. See if automatic template instantiation can be used. This is needed when heavily templated classes in Blitz++ or STL are going to be used.
  4. 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.
  5. Use Blitz++ or techniques used in it to speed up the Array arithmetic.
  6. Investigate how CORBA, DCOM, OLE, XML, ODMG, and Java can be used.


next up previous contents
Next: Other work (Tim Cornwell) Up: System (Ger van Diepen) Previous: Support of industry standards   Contents
Please send questions or comments about AIPS++ to aips2-request@nrao.edu.
Copyright © 1995-2000 Associated Universities Inc., Washington, D.C.

Return to AIPS++ Home Page
2004-08-28