variable initial value - bug? (rev. 8151)
|
09-26-2015, 04:33 PM
Post: #6
|
|||
|
|||
RE: variable initial value - bug? (rev. 8151)
If I am understanding you correctly, you are wondering why the value is not set to 1 on each execution.
If so, the reason here is simple. The variable is initialized *on compile time*. Nothing with your "local k:=1" is executed when you run your function. Rather, when you enter and then exit the editor you will see the value initialized because your program was parsed, functions created and loaded into the system and so on. Basically, the only difference between EXPORT k:=1 and LOCAL k:=1 is that that the rest of the system can see the first one, while only the functions in your file can see the second. TW Although I work for HP, the views and opinions I post here are my own. |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
variable initial value - bug? (rev. 8151) - komame - 09-26-2015, 03:03 PM
RE: variable initial value - bug? (rev. 8151) - DrD - 09-26-2015, 03:19 PM
RE: variable initial value - bug? (rev. 8151) - komame - 09-26-2015, 03:22 PM
RE: variable initial value - bug? (rev. 8151) - DrD - 09-26-2015, 04:09 PM
RE: variable initial value - bug? (rev. 8151) - xset - 09-26-2015, 04:11 PM
RE: variable initial value - bug? (rev. 8151) - Tim Wessman - 09-26-2015 04:33 PM
RE: variable initial value - bug? (rev. 8151) - komame - 09-26-2015, 06:24 PM
RE: variable initial value - bug? (rev. 8151) - Tim Wessman - 09-26-2015, 06:58 PM
RE: variable initial value - bug? (rev. 8151) - cyrille de brébisson - 09-28-2015, 06:55 AM
|
User(s) browsing this thread: 2 Guest(s)