docs.xsharp.it

User Tools

Site Tools

Trace:
xsharp_dialects

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
xsharp_dialects [2019/04/15 03:21] – wolfgangriedmannxsharp_dialects [2024/09/11 07:22] (current) – wolfgangriedmann
Line 4: Line 4:
  
 Why this? The Xbase language that was started with DBase in the MS-DOS days has several descendants, evolved each on its own, and with different syntax. Why this? The Xbase language that was started with DBase in the MS-DOS days has several descendants, evolved each on its own, and with different syntax.
 +
 Since X# was started with the intention to give a future to all or several of them, a sort of a switch is needed to differentiate them from each other. Since X# was started with the intention to give a future to all or several of them, a sort of a switch is needed to differentiate them from each other.
 +
 And please note that the Core dialect is the only one that does not need any runtime, and can build applications based only on the .NET Framework libraries. And please note that the Core dialect is the only one that does not need any runtime, and can build applications based only on the .NET Framework libraries.
  
Line 15: Line 17:
 ===== Vulcan ===== ===== Vulcan =====
 Vulcan was a (now dead) .NET evolution to the Visual Objects development environment, developed by GrafX. Vulcan was somewhat different to VO, so X# needs a proper dialect to support the migration of Vulcan applications. Vulcan was a (now dead) .NET evolution to the Visual Objects development environment, developed by GrafX. Vulcan was somewhat different to VO, so X# needs a proper dialect to support the migration of Vulcan applications.
 +===== VFP =====
 +The VFP dialect is becoming more and more important because it supports many features of the Visual FoxPro product, but the main difference is that X# is a compiler and Visual FoxPro an interpreter. The VFP dialect has also its own runtime libraries.
 ===== Harbour ===== ===== Harbour =====
 The Harbour dialect was introduced to support some language features specifically for the Harbour product, an open source compiler for Base applications. (Harbour translates mostly Xbase code to C and compiles it then with C, so it is multi-platform). The Harbour dialect was introduced to support some language features specifically for the Harbour product, an open source compiler for Base applications. (Harbour translates mostly Xbase code to C and compiles it then with C, so it is multi-platform).
xsharp_dialects.1555298484.txt.gz · Last modified: 2019/04/15 03:21 by wolfgangriedmann