Austin small
 
2 weeks from now we will have our 'X# Summit' in Austin Texas, on March 21 and March 22.
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

If you are interested to come, please send us an email at robert@xsharp.eu.
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

It's time for a short progress report. XSharp build 2.0.0.9 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.


Snowman
 
 

We are very proud that we can announce that we have just released XSharp Bandol 9 "Winter has come" to our FOX subscribers.
This new version has some new features and bug fixes. To name a few:

  • We have added support for XBase "dynamic memory variables" (PUBLIC, PRIVATE etc)
  • Some bug fixes in the compiler
  • Some bug fixes in the new macro compiler
  • Some bug fixes and new functions in the runtime
  • Some bug fixes in the VS Integration
  • We have rearranged the Project Properties dialog in the VS Integration. "Include path" and "Suppress standard header file" are no longer configuration dependent but there is one setting for all configurations.

 

{rsfiles path="fox/Compiler/XSharpSetup2Beta9Fox.zip"}


Austin small

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.

Click here for more details about the event, the preliminary list of speakers and sessions and how to reserve.

We hope to meet you in Austin !


The Christmas build (2.0.0.8) 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.