xsharp_story
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| xsharp_story [2018/01/29 13:14] – created wolfgangriedmann | xsharp_story [2024/09/11 07:16] (current) – wolfgangriedmann | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== The Story of X# ====== | ====== The Story of X# ====== | ||
| - | The origin of the X# Project has to start many years ago in the MS-DOS area with DBase III. | + | The origin of the X# Project has to start many years ago in the MS-DOS area with DBase III ([[https:// |
| DBase III was a database with a integrated language and it was very easy to write applications with it. | DBase III was a database with a integrated language and it was very easy to write applications with it. | ||
| But it had a few drawbacks: it was slow because interpreted and every user needed a licence of the product. | But it had a few drawbacks: it was slow because interpreted and every user needed a licence of the product. | ||
| Therefore a few software houses created compilers of this language to make the programs faster an run standalone. | Therefore a few software houses created compilers of this language to make the programs faster an run standalone. | ||
| - | One of this new products was FoxPro, and another, probably the most known of them, Clipper by '' | + | One of this new products was FoxPro |
| After a few years Windows come to the market, and Nantucket started the '' | After a few years Windows come to the market, and Nantucket started the '' | ||
| Unfortunately this project took a lot more than planned, but it was so promising, that one of the largest software companies of the World, CA Computer Associates (that worked mainly in the mainframe world), acquired the entire company and dedicated a lot of ressources to this project. | Unfortunately this project took a lot more than planned, but it was so promising, that one of the largest software companies of the World, CA Computer Associates (that worked mainly in the mainframe world), acquired the entire company and dedicated a lot of ressources to this project. | ||
| - | After another years of development they presented a prerelease of Visual Objects. This version was very buggy and unstable, and so many of the Clipper users were lost. | + | After another years of development they presented a prerelease of Visual Objects |
| Several years and releases after (in the meantime the compiler and the runtime were ported from Win16 to Win32), Computer Associates lost its interest in the product and decided to put it in " | Several years and releases after (in the meantime the compiler and the runtime were ported from Win16 to Win32), Computer Associates lost its interest in the product and decided to put it in " | ||
| - | At this point GrafX, s small company from Florida, but the largest Clipper and Visual Objects reseller in the world, stepped in and took over development and sales of the product, leaving the copyrights at CA. | + | At this point [[http:// |
| - | The next step was Vulcan.NET: the owner of GrafX, Brian Feldman, decided to start a new product, compatible to Visual Objects, but for the .NET Framework and using the CLR (Common Language Runtime). | + | The next step was Vulcan.NET |
| Vulcan.NET was a discrete success along the Visual Objects community and helped to discover some issues in the Visual Objects source code, contributing to make the latest versions very stable. | Vulcan.NET was a discrete success along the Visual Objects community and helped to discover some issues in the Visual Objects source code, contributing to make the latest versions very stable. | ||
| The first developer of Vulcan.NET was Don Caton, but later also Paul Piko, Robert v.d. Hulst, Chris Pyrgas, Nikos Kokkalis and Fabrice Foray were part of the development team. | The first developer of Vulcan.NET was Don Caton, but later also Paul Piko, Robert v.d. Hulst, Chris Pyrgas, Nikos Kokkalis and Fabrice Foray were part of the development team. | ||
| - | But the product had not the desired commercial success, and so GrafX decided to cut down the development team. | + | But the product had not the desired commercial success, and so GrafX decided to cut down the development team. |
| - | At this time Microsoft released the sources of their C# and VB.NET compiler as open source (called Project Roslyn), and after checking the possibilities, | + | At this time Microsoft released the sources of their C# and VB.NET compiler as open source (called Project Roslyn |
| 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. | ||
| - | Today X# is a mature product and can be used with the Vulcan.NET | + | The last step in the Vulcan.NET |
| + | 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.1517231677.txt.gz · Last modified: 2018/01/29 13:14 by wolfgangriedmann