Grasty Posted June 18, 2019 Share Posted June 18, 2019 (edited) So first things first, yes I know you can use AU3Stripper with /MergeOnly to get the line numbers to match error messages. However, the error I am getting is telling me "Error: Array variable has incorrect number of subscripts or subscript dimension range is exceeded." on Line 11179, so i did a MergeOnly but line 11179 is an EndIf. So I am wondering if there is anything that throws that line number off? I read that #pragma stuff would, but i dont have any of those. Unless the AutoIt3Wrapper compiler directives count also? But if i remove those then 11179 is a Sleep(100) .... so im a little lost. Edited June 18, 2019 by Grasty Link to comment Share on other sites More sharing options...
Developers Jos Posted June 18, 2019 Developers Share Posted June 18, 2019 I guess there is something that throws it off that I am not aware of, so would need the script to check what is happening. You could of course also run it from SciTE instead of compiling it and then it would show the real line having the issue. Jos SciTE4AutoIt3 Full installer Download page - Beta files Read before posting How to post scriptsource Forum etiquette Forum Rules Live for the present, Dream of the future, Learn from the past. Link to comment Share on other sites More sharing options...
Grasty Posted June 18, 2019 Author Share Posted June 18, 2019 (edited) Unfortunately I cant share the script, But ill see if i can reproduce it with something else. Also i ran it in Scite and it was off by 14. It was 11165 in the stripped file not 11179 Edited June 18, 2019 by Grasty Link to comment Share on other sites More sharing options...
Grasty Posted June 18, 2019 Author Share Posted June 18, 2019 I think i figured it out. We were putting the below at the top of all of our internally made UDFs. #EndRegion #EndRegion #include-once And there was a few cases where i was including a UDF that had already been included, so it was adding 2 lines to the stripped version each additional time i included the file. If i change it to the following then it resolves the issue and everything lines up again #include-once #EndRegion #EndRegion So dumb mistake on my part. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now