What languages does ModelMaker Code Explorer support?

C# Syntax support

C# support is identical in ModelMaker Code Explorer for CodeGear Delphi and ModelMaker Code Explorer for Microsoft Visual Studio.

C# for the .NET framework v1.1 up to v3.5 are fully supported with the following exceptions:

  • Preprocessor Directives (conditional defines) are not interpreted. This includes #region directives. Source region directives are maintained when sorting code. All other operations ignore regions.

Delphi Pascal syntax for CodeGear Delphi

ModelMaker Code Explorer for CodeGear Delphi assumes .pas files to be Delphi pascal syntax only.

Virtual all of standard Delphi pascal syntax is supported. Additionally MMX v5.x supports most of Delphi .NET syntax, MMX 2.x has limited support, MMX 1.x does not.

Check the user manual for details on unsupported syntax. Most important exceptions are:

  • MMX5 supports nested types in classes, all earlier versions do not support nested types.
  • indexer properties with duplicate names are not supported. The importer will emit warnings.
  • Compiler directives including (designer) regions in the class interface and method declarations are not supported. The explorer emits warnings.
  • Using the identifier escape character has some restrictions.
  • Using the qualified names has some restrictions.
  • Pure assembly methods (starting the main method's block with asm rather than begin) are not supported. Assembly inside a method is supported.
  • Property index specifiers cannot use expressions but must use a constant or numeric value.
  • Include files which for example contain part of a class interface or implementation are not supported.

Chrome Pascal syntax for Visual Studio

ModelMaker Code Explorer for Visual Studio assumes .pas files to be Chrome syntax only. Delphi pascal syntax is only available in the CodeGear IDE integrated Code Explorers.

Apart from the restrictions for Delphi Pascal mentioned above, the MMX-VS parser recognizes all Chrome syntax - except generics.

The editor and dialogs support most Chrome syntax options. The editor currently does not support: field and method implements directives, event add/remove syntax. Interface property syntax is working, but not as easy as it could be.