Modify ↓
#247 closed Feature Request (Rejected)
Global variables scope
| Reported by: | anonymous | Owned by: | |
|---|---|---|---|
| Milestone: | Component: | AutoIt | |
| Version: | Severity: | None | |
| Keywords: | Scope | Cc: |
Description
Right now the variables are visible ONLY in current script file. In this case it is impossible to create some-kind of "configuration" file where to place all configuration constants. I use EnvSet/EnvGet at this time but it's really worth because I have more then 100 constant with properties of dialogs.
It would be excellent to have some mechanism to make variable/constants visible from other script if they are included.
Thanks
Eugene...
Attachments (0)
Change History (2)
comment:1 Changed 17 years ago by Valik
- Resolution set to Rejected
- Status changed from new to closed
comment:2 Changed 17 years ago by TicketCleanup
- Milestone Future Release deleted
- Version 3.2.10.0 deleted
Automatic ticket cleanup.
Guidelines for posting comments:
- You cannot re-open a ticket but you may still leave a comment if you have additional information to add.
- In-depth discussions should take place on the forum.
For more information see the full version of the ticket guidelines here.
Note: See
TracTickets for help on using
tickets.
I suggest you think again. Look at how the UDF library is constructed and you'll find that there are files that contain nothing but global variables which are then included in one or more files where they are needed.
Closing as rejected.