- Created: 17 March 2019
This spring is going to be an exciting period. Not only will we present our product on the X# Summit in Austin, we also expect to finalize the development of the X# Runtime for VO & Vulcan.
On top of that we will finish the implementation of the XBase++ dialect and we will start with the Visual FoxPro dialect. We are also preparing to promote our product at various FoxPro events around the world.
X# is really becoming a mature product !
To celebrate this we have a special introductionary price for new subscribers to the Friends Of XSharp program. If you follow this link, or if you goto the order page on shareit and enter the coupon code "SPRING2019" you will receive a 25% discount on the normal price of € 999.
This spring sale will end on June 21st.
- Created: 17 March 2019
(Something completely different)
On the picture 2 of the robots during the training.
- Created: 12 March 2019
We have just published the detailed session schedule for the X# Summit next week in Austin.
We still have a few seats free, so you can still register.
- Created: 05 March 2019
We still have some free spots on this conference, and we'd really like to meet you there.
With the kind help of QLAdmin in Austin we have organized an interesting event.
More information about the event can be found on our website: https://www.xsharp.info/articles/other/x-summit-2019
Unfortunately the "early bird" discounts for the hotel are over, but they have rooms left: https://austincityhotel.com/
We hope to see you in Austin !
On behalf of the X# development team.
Robert van der Hulst
- Created: 26 February 2019
It's time for a short progress report. XSharp build 126.96.36.199 has been received very well by most of you.There were a few small problems and most of these have been tackled and in most cases a new DLL was created and delivered.
If you look at our GitHub repo you will have noticed that the work on the DBFCDX is progressing also. At this moment index opening and index creation is working, as well as skipping and seeking. The files created are binary compatible with the same files creates in VO and Vulcan. Actually in some rare cases we found a problem in the VO and Vulcan implementation. In the coming days we will finish the work in the CDX driver by implementing updating , deleting and inserting keys in existing indices. When that is finished we will produce a new build.
In the compiler and macro compiler a few small changes were made, nothing big,
Of course we are also preparing for the X# summit in Austin. We hope to see many of you there. If you have not registered yet, it is not too late Please send us an email and we will take care of the late registration.
- Created: 31 January 2019
We are very proud that we can announce that we have just released XSharp Bandol 9 "Winter has come" to our FOX subscribers.
- Created: 29 January 2019
The X# Summit in Austin is getting closer and closer. We are preparing everything for a great event.
If you haven't registered yet, now is the time to do so. The special hotel room price will expire on Feb 15, but apart from that we'd like to know a.s.a.p. if you are coming so we can confirm and reserve everything with the hotel and others involved.
The session schedule will become available in a week or two from now.
We hope to meet you in Austin !
- Created: 26 January 2019
The Christmas build (188.8.131.52) has been received very well, but unfortunately a few small issues in the compiler make this build difficult to use for some of our clients. The good news is that we are getting very positive reports about the level of compatibility of the runtime and the compatibility and speed of the macro compiler.
We will deliver a new version in the coming weeks that fixes the compiler problems and also has some bug fixes to the runtime and VS integration.
The biggest other change in that new build will be the support for dBase style "dynamic" variables, such as PUBLICs and PRIVATEs. We have added this to the language, even though we think that there are better ways to code, but we know that some of our (potential) customers are using it. We have also added support for the PARAMETERS keyword which is an alternative for the declared parameters and works just like the parameters in a clipper calling convention. But the compiler does not create local variables for these parameters but private variables.