We have uploaded a new compiler for our FOX subscribers to the prerelease area on this website. This interim build fixes a couple of issues found by our subscribers in beta 10.
The most important change is the way how single quoted literals are handled:
In earlier builds a single quoted literal of 1 character was always treated as a character constant. Beta 10 would treat the single quoted literal always as a string constant and then try to detect the place where it was used and convert it to a character constant when needed. Unfortunately this was not working the way it should
So the original behaviour from before Beta 10 has been restored.
Some suggestions have been made on how to change this behaviour for a future build, and we are looking into this.
- Fixed several small problems with UDCs
- Added /s (Syntax check only) commandline option. This will parse the code and detect syntax errors but will not produce any EXE or DLL output.
- Improved error messages for code where closing tokens (such as closing string delimiters and closing parentheses) are missing
- _sizeof and Sizeof will no longer generate a compiler warning about 'Unsafe code' when building for the VO and Vulcan dialect and an explicit platform x86 or x64 is selected.
- Added rules for comparing LOGIC operands. The idea is FALSE < TRUE. The resulting code will compare 0 for False with 1 for True.
- Added "ANY" as alias for "USUAL" to the VO dialect, just like in VO.
- The error numbers for the preprocessor commands #warning and #error have changed to become compatible with Roslyn. They are now XS1030 for #warning and XS1029 for #error. The error numbers XS9005 and XS9006 are unused for now but will be reused in the future
- Fix a compiler crash for a Start function without return type
We are pleased to announce that XSharp Beta 10 has been released to our FOX subscribers today.
This beta contains many new features and works together with Visual Studio 2015 and Visual Studio 2017.
Some of the highlights of this build:
- Support for User Defined Commands in the preprocessor, including Function style Defines
- Many improvements in the Visual Studio integration.
- A new 'ASTYPE' keyword, which works just like the 'as' keyword in C#. So it combines a type check and an assignment in one statement
- Full support for VO style DEFINEs The type specication is now completely optional.
- Some bug fixes
- Performance improvements for compiling assemblies with large numbers of defines and/or (_DLL) functions
For a complete list of changes look at the version history in the documentation on this website.
Our next build is scheduled around end of April, short before the XBase.Future converence in Cologne.
More and more people are using X# and are deploying their applications written in X#.
We have received some examples from our customers and have added a "gallery" of these example applications to this website. Click on the Examples menu option above to see a list of examples.
We'd love to hear from you as well and share your success story with the rest of the world. Please send us images and a short description of your application.
A great opportunity to look at successful applications is also the "Application Show" at the XBase.Future conference in April.
We'd love to see you there. Please register now !
Tomorrow, March 7 is the 20th anniversary of Visual Studio and the launch of Visual Studio 2017.
X# is ready for the event and one of the launch partners. You can watch the launch event online at this link.
To celebrate the 20th anniversary we have decided to extend the 30% discount on our Friends Of XSharp (FOX) subscription for another 3 months. Click here to subscribe to our FOX program with 30% discount.
If you are interested in offers from other launch partners, look here.
We are approaching the dead line for the “Early Bird” price for the xBase.Future conference in Cologne on April 25-27. Register now and qualify for the discount
We expect to release X# Beta 10 by the end of this week. This new build has some exciting new features, especially in the area of the Visual Studio integration (2015 & 2017). We have added support for Class and Member dropdowns, Collapsible blocks in the editor (for #regions, types, members, block statements etc), code completion, intellisense errors in the error list and editor and info tips. It is not perfect yet, but we will continue to work on this in the coming months.
In the image below you see some of these new features in action.
We have also added UDC support to the preprocessor, so almost all your “old” Clipper and Visual Objects UDCs will work with X#. You can even use the old @ SAY .. GET commands in your code, if you want, as long as you map these to meaningful function calls.
In fact we are working with a customer to migrate a Clipper/Harbour application that is full of these commands to X# !
And the good thing is: the X# Visual Studio Language integration is "smart" enough to recognize your UDC keywords and color them as if they are built-in keywords.
It is time to let you know what we have done since beta 9.Below is a list of the things that are ready and will be included in beta 10.
We have also published the contents of our help file on the website.
- We have completed support for the DEFINE keyword. The type clause is now optional. The compiler will figure out the type of the define when no type is specified.
The DEFINEs will be compiled to a Constant field of the Functions class, or a Readonly Static field, when the expression cannot be easily determined at compile time.
- We have extended the preprocessor . It now has support for #command, #translatem #xcommand and #xtranslate
- Added ASTYPE expression, similar to the AS construct in other languages. This will assign a value of the correct type or NULL when the expression is not of the correct type:
VAR someVariable := <AnExpression> ASTYPE <SomeType>
- Tested and works with Visual Studio 2017 RC 4
- We have added supports for snippets and included several code snippets in the installer
- Added support for ARM and Itanium platform types
- The parser that is used in the Windows Forms editor now also properly handles background images in resource files. Both images in the resx for the form and also background images in the shared project resources
- We have added Nuget support for our project system.
- Added a project property to control how Managed file resources are included: Use Vulcan Compatible Managed Resources
- Fixes several problems with dependent items
- Added implementation of the OAProject.Imports property, which is used by JetBrains
- Fixed a problem converting WPF style projects