OmniPascal 0.12.0 – Add units to uses clauses

This GIF shows how “Implement interface” automatically adds System.TypInfo to the uses clause and how the new “Add unit to uses” command works.

New features:
– Execute Add unit to uses in order to add a unit to a uses clause without navigating to the top. Open the command palette (by pressing F1 or CTRL+SHIFT+P) and type “Add unit to uses”. Select the uses clause and a list of all available units will appear. Select the one you want and press enter. The command is also bound to ALT+U
– Automatic implementation of interfaces adds missing units to the uses clause
– Member of typed pointers can be resolved

– Creation of errors and warnings does no longer stop working after a while
– Constants in classes are now resolved properly
– Indexed access on constant resolves now to the definition of that constant / constant array
– Fixed random crashes

Notable changes:
– General performance improvements. Especially startup and code completion are much faster.

Version 0.11.0 – Implement interfaces

Change log:

  • New warnings for incomplete interface implementations
  • Quickfixes for incomplete interface implementations create method declarations and implementation stubs
  • Fixed compatibility to Visual Studio Code 1.7.0
  • Improved the text that pops up up when hovering a constant
  • Fixed code highlighting in hover popup
  • Bugfix: Hovering a method call now shows the signature of the method’s declaration instead of its implementation
  • Bugfix: “Implement method” produced broken code for methods with open array parameters
  • Bugfix: Method resolution clauses were creating warnings for missing implementations
  • Bugfix: UTF8 files with and without BOM are now handled properly
  • Bugfix: Wrong declaration found when a method parameter has the same as a property
  • Bugfix: Directories having the “hidden” or “system” attribute set were invisible to OmniPascal
  • Bugfix: Message “Ordner nicht angegeben” when opening .pas file from explorer
  • Calls to members of a constructor’s return type can be resolved: Example: TObject.Create.Free
  • Improved performance and stability

OmniPascal 0.10.0 – Intrinsic symbols and castings

– Members of type casted identifiers can be resolved
– Code completion works even when working with type casts
– Basic data types like Integer or String appear in code completion
– Added support for Delphi Intrinsic Routines for Windows 32 platform
– True, False and Nil now appear in code completion
– Added support for pointer types

– Names of nested types in generic classes couldn’t be resolved in method implementations
– Names of nested strict private types can be resolved
– Code completion list doesn’t grow anymore when triggered multiple times in classes which inherit from a specialized generic class
– Fixed occasional crashes of OmniPascalServer.exe when editing code with multiple cursors
– Calls to overloaded methods weren’t always resolved correctly based on the parameter count. (Resolving calls to overloaded methods still doesn’t work when multiple versions of a method accept the same amount of parameters)
– Members of items in generic arrays can be resolved
– Name resolving and code completion for symbols defined in the implementation section now works in initialization and finalization section

…as well as some speed improvements.

OmniPascal 0.9 – Namespaces and more

– The search path will be indexed on start up
– Code completion in uses sections suggests known unit names
– Support for full qualified names like System.Classes.TStringList
– Code completion only suggests types and namespaces when only a type name makes sense in the current context
– Code completion in interface declarations suggests a GUID
– An error is displayed when a unit name doesn’t match its file name
– An error is displayed for duplicate entries in uses section
– An error is displayed for unresolvable entries in uses sections
– A lightbulb appears on unresolvable uses entries which allows to create that file in the current folder
– Hints of hoverered unit names in uses sections look nicer
– Definitions of redeclared properties can be resolved and are part of code completion
– It’s possible to jump to the initial declaration of a redeclared property
– Support for hidden namespaces in uses section (for example “Classes” can be resolved to “System.Classes”)
– Code completion is disabled when defining a new symbol

– Code completion used the wrong scope from time to time especially when hitting the dot inside of if-statements or brackets.
– Signature help now highlights the current parameter as soon as the comma is entered
– Signature help didn’t work when used on a member’s method of an object like ObjectA.Member.Find()
– Warnings for incomplete method definitions in included files were created
– Go to a definition of a symbol which is defined in an included file no longer opens the including file but the include file
– Symbol definitions of included files were part of outlining
– No warnings have been created for missing implementations of overloaded methods if one of those methods already had an implementation
– UTF8 files with BOM header can be parsed now
– Protected symbols which should be invisible were part of code completion in special cases
– References to out parameters without type information (void types) can be found
– Quickinfo for variables of type “file” contained no type information
– Code completion showed empty suggestion item
– Code completion in specialized generic descendants didn’t include protected members of non generic base classes
– Parameterized type names in static method calls couldn’t be resolved
– Method names in static method calls on parameterized type names couldn’t be resolved
…as well as some speed improvements.

OmniPascal 0.8.1 released

New features
– Syntax errors are displayed in the editor
– Method definitions without implementations produce warnings
– Warnings for missing implementations provide a quickfix that creates an empty implementation stub for it. TIP: Open the lightbulb with CTRL+.
– Additional search paths can be defined in configuration file using the "objectpascal.searchPath" parameter. Paths are separated by ;. TIP: "D:\\ThirdPartyComponents\\*" will add the folder "D:\ThirdPartyComponents and all its subfolders recursively to the search path.
– DPR files have now support for code completion
– DPR files have now support for outlining

Bug fixes
– Code completion cleaned up from internal compiler methods
– It was impossible to go to the declaration of a procedure that was not a class member
– Fixed undefined internal file state that occured from time to time
– Parameters were not always displayed correctly when hovering a method

– Toggle Method declaration/implementation has become more error tolerant
– Outlining huge files is >10 times faster now
– Create code completions in huge files is >20 times faster now
– OmniPascal generally runs faster and consumes less memory
– Some words like as, mod,div etc. are temporarily not displayed as operators (gray in dark default theme) but as keywords (blue). This change has become necassary as Visual Studio Code broke some details in syntax highlighting with the latest release. Probably operators will be displayed in gray again in the future.

Announcing OmniPascal – Open Preview

OmniPascal is the newest way to edit Delphi and Free Pascal code.  It’s going to support all language features Delphi knows. It will give you code completion, quick code navigation, great syntax highlighting and much more.

Today OmniPascal becomes available for open preview! The current version supports already a lot of useful features as you can see on And there is much more about to come in the future. OmniPascal aims to become the greatest code editing experience Delphi developers have ever seen.

You will find the latest news about the project always here on

Share your thoughts about OmniPascal. Help us creating the best tool Delphi and Free Pascal developers deserve!