![]() ![]() dcu file for each unit or – when you are building a package, a. When you compile a library (we'll ignore executables for this post) in Delphi, your code gets compiled into a binary and a. Delphi also has its own ways of dealing with simple types such as Strings (Island strings are Objects, Delphi strings are not), and so on. This is, of course, a highly oversimplified description.ĭelphi uses its very own object format for classes you create in your Delphi project, and these classes descend from a type called TObject, and they work very differently from Island objects. Essentially it describes the types you created, so that when you use your library from a different project, the compiler knows what types there are and how to find them in the. fx file that contains meta-data about your code. ![]() For libraries, the Elements compiler also emits a. When you compile an Island projects, these objects (and other stuff) get compiled into an executable (an. All Island objects descend (directly or indirectly) from this type. When you create a class in Elements (we're focusing on using the Island platform for native Windows, Linux or macOS projects, for the purpose of this article), these objects are laid out using a system defined by our own compiler, and descending from a type called System.Object that's defined in the Island RTL base library. To start with, the Elements compiler and the Delphi compiler use very different object models. You might just reuse some code in your new Island app – or you might just bring a full VCL app over into Fire or Water, and start using Oxygene's more advanced Object Pascal language all across your code.īut lets step a bit back and ask: How Does This Work? Inter-operability between Elements and Delphi scales to your needs. Always wanted to create a VCL form in C#? Now you can! The possibilities here are endless, from merely (re)using few Delphi APIs you really like and are familiar with, to building entire new application on top of VCL or FireMonkey, but with the full power and flexibility of the Elements compiler, for the code you write. You can also use third-party component libraries and, of course, your own Delphi-compiled code – directly and seamlessly from Oxygene, C#, Mercury, Java, Swift or even Go. With the just-announced Elements Twelve, we have added a major and long-requested new feature to our native-code "Island" platform: support for the Embarcadero Delphi class/object model and – with that – the ability to consume just about any* Delphi APIs from your Elements projects, including the Visual Component Library (VCL), FireMonkey, dbGo, DBX, and so on. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |