InterSystems IRIS Documents
Documents include class definitions, routines, and data transformations. InterSystems IRIS records information such as whether a document has changed since the last compilation. Your source control system treats each document as a separate unit.
In InterSystems IRIS and your source control system, you work within one namespace at a time.
Deciding How to Map Internal and External Names
Each document has two names:
-
An internal name. For example, the name used in the Open dialog box in Studio.
-
An external name. The fully-qualified path to the file in the file system. Because of differences in how file paths are constructed between supported InterSystems IRIS platforms, it is not possible to provide a meaningful default.
Creating a bidirectional mapping between internal and external names may be one of the most challenging parts of implementing a source control system. This mapping is customer-specific and should be considered carefully. You want to group similar items. For example, the sample uses the following directory structure:
-
Class files are in the cls subdirectory, which contains subdirectories corresponding to the package hierarchy of the classes.
-
.INT routines are in the int subdirectory.
-
.MAC routines are in the mac subdirectory.
For example:
If you have large numbers of routines, you might prefer to group routines into subdirectories, perhaps by function.