Any additional patterns are appended to the language definition File Extensions list following the primary pattern. File extensions are used to automatically associate source files with a language definition. For example, if the file extension "cbl" is defined for the COBOL language definition, any file with the "cbl" extension - MORTGAGE.cbl - will automatically be associated with the COBOL language definition and be built as a COBOL language item.
A language definition may encompass multiple file extensions. Additional file extensions should be defined in the Additional patterns field. When you are defining additional file extensions, make sure that each extension identified is unique within the EWM™ repository. Separate each additional file extension with a comma:
cbl,cobol,cobolMortgage,cobolAccounting
The language definition File Extensions list provides a convenient method to associate source files with language definitions which then determines how a file is to be built. Defining and using file extensions is not mandatory, but it is highly recommended. The alternative to using file extensions is to individually associate each source file with a language definition within the source code management system. The alternative method is tedious to set up and maintain and will result in some extra overhead when a file is processed for a build. Using the alternative method is more appropriate as an override mechanism for specific source files or special situations.