However, the development of Dragon Version4 is made with modern quality assurance (QA) traceability techniques. This traceability goal is achieved through the application of versioning control (using Subversion) and issue tracking systems to the following project components:

• Fortran sources of the Version4 components
• Non-regression tests
• Software documentation
• Scripts of the NJOY-based library production system

In Dragon 3.0x:
LINK_LIST LIBRARY TRACK GEOM ;
...
UTL: LIBRARY :: STEP UP MACROLIB ;
TRACK := BIVACA: GEOM LIBRARY ;
UTL: LIBRARY :: STEP DOWN ;


In Dragon Version4:
LINK_LIST MACRO LIBRARY TRACK GEOM ;
...
MACRO := LIBRARY :: STEP UP MACROLIB ;
TRACK := BIVACA: GEOM MACRO ;


Also, a few modules, such as JPMT:, SAD:, PER: and MCU: are not available in Dragon Version4. The capabilities of modules EXCELL: and MOCC: have been integrated in ASM: and FLU:, respectively.

• A native build is possible, provided that Microsoft Visual Studio and Intel Visual Fortran are available. A script named instver4.bat is available as of Version 4.0.4 to create executables (.exe) from a MS-DOS command window. Follow the following steps:
  • Click Start, point to All Programs, Intel(R) Software Development Tools, Intel(R) Visual Fortran Compiler Professional and finally Fortran Build Environment for applications running on IA-32. The Visual Studio Command Prompt automatically sets the correct paths of both C and Fortran compilers, together with their associated libraries.
  • In the command window, type
    cd %homepath%\Version4\
.\script\instver4
• A "Unix-type" build is possible, provided that Cygwin is properly installed on your PC. Cygwin is a native implementation of a Unix shell. After installation of Cygwin, you obtain a native Unix terminal window where all Version4 components can be executed.

A tutorial is available to explain the installation procedure on a Mac.

Enhancements to Version4 can be written as procedure files in CLE-2000 language or as modifications to the Fortran source. CLE-2000 procedures or new Fortran modules written by you are not covered by the LGPL. We encourage you to release your Fortran source enhancements under the LGPL for inclusion in future versions of Version4.

SEQ_ASCII Fig_reg :: FILE 'Fig_reg.ps' ;

Moreover, if the main CLE-2000 dataset file is named data.x2m, a data.save script file must be defined to recover the Fig_reg.ps file. An example of such a data.save script file follows:

#!/bin/sh
#
if [ $# = 0 ]
then
  echo "usage: data.save directory" 1>&2
  exit 1
fi
echo access data.save
MACH=`uname -s`
Sysx="`echo $MACH | cut -b -6`"
if [ $Sysx = "CYGWIN" ]; then
  MACH=`uname -o`
elif [ $Sysx = "AIX" ]; then
  MACH=`uname -s`
else
  MACH=`uname -sm | sed 's/[ ]/_/'`
fi
ls -l
mv *.ps $1/"$MACH"
echo "data.save completed"


This script file must be set as executable using a Bourne directive:

chmod 755 data.save