Comment's causing errors?

Jfullernz · **Thanked:** 0 time(s) **Posted:** Mon Oct 25, 2021 3:59 am

Ok issue when attempting to save my macro - error of trying to parse "ing"
the line at fault is a comment line

Code:

// Walking through town not functioning

this errors

Code:

// Walking through town not working

this does not error.

It looks like its seeing the substr of function in the comment and trying to use it as a function?

Syrifina · **Thanked:** 0 time(s) **Posted:** Mon Oct 25, 2021 4:07 pm

I couldn't duplicate that problem. I tested with the words you used and even with other combinations of "function" including the word itself and I didn't receive any errors.

If you make a mistake in the syntax it would look like this:

Attachment:

Capture2.PNG [ 11.98 KiB | Viewed 14587 times ]

If it just gave a line number, then it was probably not that line.

I'm sure as a programmer this is going to sound annoying, but BEM doesn't count every line when reporting parsing errors...at least not all the time. For example, it usually only counts the first "begin" if there are multiple begin/end statements; otherwise it doesn't include any other begin/end statements in the count. If it wasn't a commenting syntax error like above, then it wouldn't count any comments either; like in this example:

Attachment:

Capture3.PNG [ 11.81 KiB | Viewed 14587 times ]

When counting you skip over the "begin" because there is only one set (begin/end), you skip over the comments, and then you get the correct error at line 5 which is the mouse.drag missing required information.

If you take the same example and re-order the comments, you can see that if you counted every line it would appear as it was pointing the commented line with "function" in it, but it is still pointing to the mouse.drag line (you have to skip the comments):

Syrifina · **Thanked:** 0 time(s) **Posted:** Mon Oct 25, 2021 4:12 pm

If you still have the problem or can duplicate it, please post the script and the error message and I'll take a look at it.

Jfullernz · **Thanked:** 0 time(s) **Posted:** Tue Oct 26, 2021 12:17 am

Still does it. I have attached to screenshots showing the only difference between them. literally just have to change the comments line work of working to functioning and it fails
the abort is there because the function is failing, with the comment to explain why

Code:

     begin
          if  Variable.Exists("InTown")
               begin
                    Macro.Abort()
                    // Walking through town not working
                    Function.Execute("CheckHP")
                    if  Variable.Exists("UseAOE")
                         begin
                              Variable.Remove("UseAOE")
                         end
                    if  Variable.Exists("CollectBounty")
                         begin
                              if  Variable.Exists("CollectBounty")
                                   begin
                                        if  Variable.Does not exist("BountyComplete")
                                             begin
                                                  Window.Display html dialog("Debugging", "280", "25", "yes", "Going to Bounty Board")
                                                  // Function.Execute("ClaimBounty")
                                                  //                         Function.Execute("ReturnFromBountyBoard")
                                             end
                                        Variable.Remove("CollectBounty")
                                   end
                         end
                    if  Variable.Does not exist("ClaimBounty")
                         begin
                              // Function.Execute("LeaveTown")
                         end
                    Macro.Break from loop("no")
               end
     end
function

Syrifina · **Thanked:** 1 time(s) **Posted:** Tue Oct 26, 2021 1:52 am

Got it; I didn't test it within a function...so that makes more sense.

It's because a function ends with "function", so yes it will give an error because it still reads it and thinks that's the end of the function...only because it's case-sensitive. If you change it to a capital "F" then it won't do it; only the lower case "f".
- I see your point though. I'll make a note of it for future updates; see if there's anything we can do.

Jfullernz · **Thanked:** 0 time(s) **Posted:** Tue Oct 26, 2021 2:26 am

Thank you

Typically in any programming language I've used in the past, a comment line is exactly that - a comment - and doesn't attempt to compile it along with the functions. This is what was getting me confused since it wasnt being treated as a comment line. and if it is trying to process that, I wonder how many commented code lines to disable are not actually being disabled?

Blue Eye Macro

Comment's causing errors?