Getting Started

Documentation

Glish

Learn More

Programming

Contact Us

Version 1.9 Build 1367

News	FAQ
Search	Home

Future work

The following list indicates some areas of development/refinement in AIPS++ system management. Some of the jobs listed could be done in under an hour, others would take several days.

• exhale should limit the number of incremental update files maintained in ãips++/master_ftp to about two-weeks worth.

• exhale should create a new RCS version when it creates a new base release.

• When inhale fetches a new base release from the master it should also update the import_ftp and code_ftp directories for redistribution to local end-users.

• Bug fixes should be stored in ãips++/code_ftp and a special-purpose script should be provided to fetch and apply them. configure needs to know that bug fixes must be unloaded after the base release files.

• As far as is possible, configure should check to see that entries made in the makedefs and aipsrc files are valid.

• Deletions from the master must be propagated to the slave.

• updatelib should test library modules (other than Input.o) to ensure they don't contain a main().

• ai should test the code being checked in to ensure that it conforms to AIPS++ coding style rules.

• All of the AIPS++ shell scripts are written in Bourne shell. It may be advantageous in the long run to convert them to perl which is probably more portable. The exceptions are aipsinit, which must have Bourne and C-shell versions, and configure which can't assume that perl is available, and would have to install it if it wasn't.

• man pages are required for ai, aipshosts, ao, au, configure, makedefs, and updatelib.

• Makefile enhancements:
  • At the moment make will recompile everything if one header file has been changed because the makefiles don't contain a proper dependency analysis. Dependency information should be generated.

  • Separate optimized/nodebug (sharable) and nooptimize/debug (static) libraries should be maintained.

  • Library and application rebuilds should be structured in such a way that several machines can work together to rebuild the system.

  • The makefile target in all makefiles should copy from the AIPS++ code directory if no rcs directory is present.

  • Directory search should be used for link libraries.

  • A makefile is required for the ãips++/code/kernel/doc areas.