https://doc.castsoftware.com/export-v2/extend/create-a-new-extension/creating-or-modifying-a-custom-extension-using-the-cast-universal-analyzer-framework/universal-analyzer-language-packages/xxxmetamodel-xml-file/Recent content in xxxMetaModel.xml file on Documentation - V2Hugoenhttps://doc.castsoftware.com/export-v2/extend/create-a-new-extension/creating-or-modifying-a-custom-extension-using-the-cast-universal-analyzer-framework/universal-analyzer-language-packages/xxxmetamodel-xml-file/defining-a-new-language/Mon, 01 Jan 0001 00:00:00 +0000https://doc.castsoftware.com/export-v2/extend/create-a-new-extension/creating-or-modifying-a-custom-extension-using-the-cast-universal-analyzer-framework/universal-analyzer-language-packages/xxxmetamodel-xml-file/defining-a-new-language/<h2 id="introduction">Introduction</h2> <p>Defining a new language is necessary if you want to use the Universal Analyzer to directly analyze source code, or you want to use the <strong>Universal Importer</strong> tool to import data generated by an external analyzer. The first step involves defining the language and then the objects that form the language you want to analyze. This is done by editing the <strong>xxxMetaModel.xml</strong> file in your package.</p> <div class="alert alert-info" role="alert"><div class="h4 alert-heading" role="heading">Info</div> <p>Please note the following rules pertaining to the naming of types and categories in your xxxMetaModel.xml file:</p>