xsharp_story
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
xsharp_story [2018/03/04 18:20] – wolfgangriedmann | xsharp_story [2024/09/11 07:16] (current) – wolfgangriedmann | ||
---|---|---|---|
Line 25: | Line 25: | ||
But very fast the new X# compiler supported features Vulcan.NET never had supported, like the definition of generics, LinQ, AnyCPU platform and many more. And on the other side, it was more compatible to Visual Objects than Vulcan.NET ever was. | But very fast the new X# compiler supported features Vulcan.NET never had supported, like the definition of generics, LinQ, AnyCPU platform and many more. And on the other side, it was more compatible to Visual Objects than Vulcan.NET ever was. | ||
- | The last stone in the Vulcan.NET story was the announcement on the GrafX website: "As of 12/31/2017 GrafX Database Systems Inc. is closed." | + | The last step in the Vulcan.NET story was the announcement on the GrafX website: "As of 12/31/2017 GrafX Database Systems Inc. is closed." |
- | + | ||
- | + | ||
- | Today X# is a mature product and can be used with the Vulcan.NET runtime and class libraries, and the work on their own runtime and macro compiler is in process. | + | |
+ | Today X# is a mature product and comes with its own runtime libraries and macrocompiler. | ||
+ | Different xBase flavors are supported, and since the current developers came from VO, the VO dialect is the most advanced dialect. But many requests have also come from th Visual FoxPro community, and therefore also the VFP dialect has many features. There is also some support for the Xbase++ dialect and the Harbour dialect. | ||
+ | The compiler can also be used with the Vulcan.NET runtime and class libraries for compatibility. | ||
xsharp_story.1520187626.txt.gz · Last modified: 2018/03/04 18:20 by wolfgangriedmann