variable initial value - bug? (rev. 8151)
|
09-26-2015, 06:24 PM
Post: #7
|
|||
|
|||
RE: variable initial value - bug? (rev. 8151)
Quote: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. Does this mean that all local variables defined as program global scope are kept in memory and contain the last values set during the program execution? I have noticed that sometimes going into the Program Catalog after editing my program its size is 15kb (the program creates a long list and saves it to a variable), but after I run it its size is increased to 20KB. After editing once again size is reduced to 15kb. Is the reason for this is that after the end of the execution all the time in the memory are held values of some variables and they are only reinitialized after editing/parsign? Piotr |
|||
« 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: 1 Guest(s)