Star-Dust Expert Licensed User Longtime User Nov 11, 2018 #1 I used Erel's B4XEval Class and made a small change to fit my FlexGrid library. But when I execute the code in DEBUG it marks me a nonexistent error: Variable not declared, in reality it is not so. Now I've created an example code to reproduce the problem but it marks another nonexistent error: 'Current declaration does not match previous one.' I attach the code and the error message at the bottom This error does not occur in RELEASE (and DEBUG LEGACY) mode. BUT compile perfectly Last edited: Nov 11, 2018
I used Erel's B4XEval Class and made a small change to fit my FlexGrid library. But when I execute the code in DEBUG it marks me a nonexistent error: Variable not declared, in reality it is not so. Now I've created an example code to reproduce the problem but it marks another nonexistent error: 'Current declaration does not match previous one.' I attach the code and the error message at the bottom This error does not occur in RELEASE (and DEBUG LEGACY) mode. BUT compile perfectly
stevel05 Expert Licensed User Longtime User Nov 11, 2018 #2 It is because there are loops that use Row and Col as indexes that aren't declared first. When they are then declared as Int, it is considered to be an error. Add the line : Code: Copy Dim Row,Col As Int as line 85 in EVal module
It is because there are loops that use Row and Col as indexes that aren't declared first. When they are then declared as Int, it is considered to be an error. Add the line : Code: Copy Dim Row,Col As Int as line 85 in EVal module
Star-Dust Expert Licensed User Longtime User Nov 11, 2018 #3 This is the incriminated Sub. In my opinion it is a BUGS, because compiled works correctly as in DEBUG LEGACY. It should always mark it error or never. P.S.: The code is from Erel, so if you wrote it the code will be right and the debugging is wrong Last edited: Nov 11, 2018
This is the incriminated Sub. In my opinion it is a BUGS, because compiled works correctly as in DEBUG LEGACY. It should always mark it error or never. P.S.: The code is from Erel, so if you wrote it the code will be right and the debugging is wrong
stevel05 Expert Licensed User Longtime User Nov 11, 2018 #4 I believe that the Legacy Debugger is deprecated. The code is from Erel, so if you wrote it the code will be right Click to expand... Just an oversight I'm sure.
I believe that the Legacy Debugger is deprecated. The code is from Erel, so if you wrote it the code will be right Click to expand... Just an oversight I'm sure.
Star-Dust Expert Licensed User Longtime User Nov 11, 2018 #5 Legacy has been deprecated. But Release is not deprecated and compiles perfectly, the code is correct.
Legacy has been deprecated. But Release is not deprecated and compiles perfectly, the code is correct.
stevel05 Expert Licensed User Longtime User Nov 11, 2018 #6 https://www.b4x.com/android/forum/t...oes-not-match-previous-one.57985/#post-365326
