Articles

A quick message to inform you of some of the things that are happening in the X# team.

1. We know that many of you (just like us) love footbal (soccer). Wouldn't it be great if you could combine soccer with technology.
   It turns out you can. At the university of Twente a team of you students is working on Robot soccer.
   We like that idea so much that we have signed up as sponsors: https://roboteamtwente.nl/
   
2. We have received a request from the community to start adding support for the XBase++ dialect to the compiler. We have analyzed the language differences, and it seems that there are very few differences. The biggest change is the way that classes are declared. XBase++ follows the "Class(y)" style of class declaration (Anton van Straatens OOP extension to the Clipper language).
   The class declaration syntax for XBase++ is also almost identical as the syntax for (x)Harbour. So we might combine the two.
   At this moment we are working on the XBase++ support in the parser and compiler.
   After that we will add runtime support for the XBase++ dialect.
   This new dialect will most likely not be included in the upcoming releases , but we still would like to inform you.
   Our XBase++ customer wants to run his code in a webservice. So no UI. Most likely we will create some kind of poor man's UI that emulates the CRT windows on the console.
   If you are interested in XBase++ support and would like to contribute on the UI or specific runtime functions (maybe a library like Sql Express or XBase Tools) please contact us.

 

---

We have released X# Bandol Beta 7. This build fixes some issues found in Beta 6, adds the Hybrid classes that were also present in Vulcan (thanks Paul Piko) and some functions that we had overlooked in previous betas.

---

We are very happy to announce that we have uploaded X# Bandol Beta 6 for our FOX subscribers.
This build adds the RDD support to the runtime including the DBF-DBT-NTX RDD and the advantage RDDs. We have also included DBF-FPT. CDX is not available yet.

We have also included compiled versions of the VO SDK Class libraries that are compiled against the X# runtime.
The complete list of changes can be downloaded from https://www.xsharp.info/itm-downloads/download?path=general%252FReadme%252Fwhatsnew2006.rtf.

---

You haven't heard from us in a while, so some of you might be wondering what we are doing.
Well, the answer is that we are working very hard (our wifes say too hard <g>) to finish the X# runtime.
At this moment the status of the runtime is:

• 97 percent of the functions are implemented, tested and working.
• The DBF/DBT RDD is implemented and working
• The Advantage RDD  is implemented and working (you can use this for DBF/DBT/NTX, DBF/FPT/CDX, ADT/ADM/ADI and the various SQL variants)
• The NTX RDD is almost completed
• The FPT layer for DBF/FPT/CDX is implemented and working. We have not started with CDX. If you need DBF/FPT/CDX you can use the Advantage RDD in combination with the Advantage local server for now.
• The VO SDK is compiling without errors (which means that also all the undocumented VO stuff has been implemented).
• And everything is AnyCPU and thread safe. Of course when you use the GUI classes from the VO SDK and/or the SQL Classes then you are limited to x86 because these classes are not designed for AnyCPU.

We have also made some improvements in the Visual Studio support

• Opening of very large Solutions now is MUCH faster
• We have fixed some issues that were reported

Finally we have made some changes to the compiler that were needed for some special cases related to compiling the VO SDK (this SDK contains some really ugly code...) and we fixed some issues reported by our customers.

We plan to publish our "work in progress" in a new beta for FOX subscribers end of next week, that means if we can succeed to reach our goal:
Our intention for the next beta is that applications that use the standard VO SDK libraries and no 3rd party components should work with minimal changes.
You may have to change the RDD name, but the rest should work.
If you have already changed your code for Vulcan you should be able to swap the Vulcan runtime and Vulcan SDK libraries for our Runtime and SDK libraries, recompile your code and run.

 

---