-
-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create _WinDate structure that stored Date values in a VO struct just like VO does. #773
Comments
…sents a Date inside a VOSTRUCT or UNION. Fixes #X-Sharp/XSharpPublic/issues/773
Wow, great! |
* [Compiler tests] Added tests for X-Sharp/XSharpPublic#770 and X-Sharp/XSharpPublic#771 * [Compiler] Fixes #X-Sharp/XSharpPublic/issues/771 Create Usuals with IsByRef flag set to TRUE for OUT variables. Also modified the RefKind for the Temporary local because the SynthesizedLocal type does not like RefKind.Out. * [Tests] Added new group and moved C799 to fixed tests * [Compiler] Added support + test for the new __WinDate type that represents a Date inside a VOSTRUCT or UNION. Fixes #X-Sharp/XSharpPublic/issues/773 * Fixes #X-Sharp/XSharpPublic/issues/603 and adds test case R800 * Fixes #X-Sharp/XSharpPublic/issues/772 * Added test for #X-Sharp/XSharpPublic/issues/772 * Updated test R742 for the FoxPro array access with parenthesized indices * [Compiler] Renamed Compiler option fox2 to FoxArraySupport. Fixes #X-Sharp/XSharpPublic/issues/746 and R742 * Updated several keywords * Updated Doc files * [Compiler] More changes for FoxPro Array support. Also added test to runtime tests * [Compiler tests] Added C802 - Internal Compiler Error with multiple PRIVATE &varName commands for X-Sharp/XSharpPublic#780 * [Compiler] Fixes #X-Sharp/XSharpPublic/issues/780 Fixes C802. marks test as fixed. * [Compiler] temporary update FoxPro SQL * [Compiler] Defaults for USUAL are noe default(usual) for non Fox dialects, and __Usual._NIL for the FoxPro dialect * [Compiler] Updated version number. VSParser does not run the Preprocessor when ParserLevel = ParseLevel.Lex * [Compiler] Only FoxPro dialect now uses __Usual._NIL for empty usuals. We now allow __Usual.NIL to be a field (Vulcan) or a property. Also added test R803 to make sure that NIL is never overwritten * [Tests] Added assertions to R803 * [Compiler] Fix problem with missing arguments passed to a function that expects a REF USUAL or OUT USUAL. A Previous solution could lead to the __Usual._NIL value to become corrupted. * [tests] Removed WAIT from 2 tests and marked tests as fixed. * [Compiler] Change error message when they are passing NIL to a method / function that has a REF or OUT parameter * [tests] Updated Runtime to 2.9 Co-authored-by: cpyrgas <chris@xsharp.eu>
This has caused some problems unfortunately. This is from Leonid's code, which was compiling and running without errors previously:
|
I think this are 2 different issues:
|
I reviewed case #1. This error does not happen because there are numeric operators on the __WinDate type, but because there are several numeric operators on the Date Type. We have these operators:
The compiler does not know which one to choose. BTW the operation |
…r problems with the __WinBool type
Robert,
I just did this for an example so that for both cases I declare one variable. In a real application, the following code (template): |
Robert,
|
Leonid, |
Robert, maybe it's better to roll back completely the change with introducing _WinDate for now? I am afraid there will be problems in other people's code as well because of that. What would be the consequences of reverting the change (for now)? I think it's only that DATEs in structures will not be binary equal to VO, which is not really a big problem, is that right? |
Chris, |
I am sure there are more. The code in the asbau project used that as well. |
Guys, In my projects, I have not found any other problems with the __WinDate type, besides the ones I described above. If suddenly this information will be useful to you for making a decision. For my part, I can only hope that these fixes, if they are not complex, will still get to version 2.9 or at least to the next patch after it. Since I have a lot of similar code. |
Leonid, The LOGIC text in the debugger is a copy/paste error and very easy to fix. |
Leonid, |
Robert, all the issues mentioned here #773 (comment) still exist |
Arghh, thought the test (C804) had included those, but it doesn't. Updating it now. |
Robert, |
…warded to the __Date type. Also fixed a problem in __Date:Subtract(USUAL)
Confirm fixed |
Robert, |
See #735
The text was updated successfully, but these errors were encountered: