- Created: 10 July 2017
We have just released XSharp "Anjou" Update 1.
This update fixes some issues that were found in the last week:
- Fixed a problem with VERY old versions of the Vulcan Runtime (early Vulcan 2 versions)
- Variables declared as DIM Byte and similar are now Pinned by the compiler
- [Return] attribute was not properly handled by the compiler. This has been fixed
- Compound Assignment (u+= f or -=) from USUAL and FLOAT were causing a stackoverflow at runtime caused by a problem in the Vulcan Runtime. These expressions now generate a compiler error with the suggestion to change to a simple assignment ( u := u + f)
Visual Studio Integration
- Project References between XSharp Projects were also loaded as assemblyreference when resolving types. This could lead to speed problems and unnecessary memory usage
- Improved the speed of the construction of Completion Lists (such as methods and fields for a type).
- We have also added Completion List Tabs, where you can see fields, properties, methods etc. on separate tabs. You can enable/disable this in the Tools/Options/Text Editor/XSharp/Intellisense options page.
- We have added a check to make sure that the default namespace for a X# project cannot contain a whitespace character
On behalf of the Devteam I want to thank you all for the nice feedback that we got in the last week.This is really appreciated !
Only for curiosity: Why is the release called "Anjou"?
a former province of western France, on the Loire River. It was an English possession 1154–1204
This is what Bing told me.
Let's see if Fabrice or Robert will step in here..
May be, we should wait for the next release to see if the name is random, or on purpose ;)
Maybe it is time we tell them about the battle of Anjou in 42 AD, where the Gaul Fabrix Fortix beat the Roman general Brutus HomusCampus, which was the inspiration for Goscinny and Uderzo for their famous strip books.
OK, I guess it would had been better to simply admit that we indeed used way too many subversion numbersNow that's true greatness! ;)
One nitpick: "22.214.171.124" ? Given, that even folks like @Postgres switched to a 1 digit scheme <G>, i'd left it at 1.0.2