Modify ↓
Opened 15 years ago
Closed 15 years ago
#1776 closed Bug (No Bug)
Strange MustDeclareVars Behavior
| Reported by: | Owned by: | ||
|---|---|---|---|
| Milestone: | Component: | AutoIt | |
| Version: | 3.3.6.1 | Severity: | None |
| Keywords: | mustdeclarevars func runtime | Cc: |
Description
When Opt("MustDeclareVars",1) is in effect, under certain conditions which I can not accurately reproduce yet, a runtime error is given when constructing a function such like
Opt("MustDeclareVars",1)
Func FName($badlytriggered)
Return
EndFunc
I have worked around this bug by simply declaring the variable in question as global:
; Awkward but necessary bug fix Global $badlytriggered
I'll keep trying to accurately reproduce this bug, it won't just reproduce easily. Something in a simple local budget tracking application is causing the trigger.
Attachments (0)
Change History (2)
comment:1 by , 15 years ago
comment:2 by , 15 years ago
| Resolution: | → No Bug |
|---|---|
| Status: | new → closed |
You do not have a bug to report so you should not be reporting a bug. You need the support forum until you can clearly demonstrate otherwise.
Note:
See TracTickets
for help on using tickets.

Try stripping down your code(copy) while preserving the error.
But only that target error, correct all other before the next removal step.
Adding a dummy function that can be used as a substitute for function code that you remove could help.