Variables – Talk
Jump to navigation
Jump to search
mNo edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
::Yes I did. That's what threw me. "scope does not apply to global variables"... my experience shows it does. --[[User:Doolittle|Doolittle]] 23:24, 12 September 2007 (CEST) | ::Yes I did. That's what threw me. "scope does not apply to global variables"... my experience shows it does. --[[User:Doolittle|Doolittle]] 23:24, 12 September 2007 (CEST) | ||
:::Are you 100% sure? I have yet to see a global variable contradict the expect behaviour. Could you point us to an example mission? [[User:UNN|UNN]] 02:10, 13 September 2007 (CEST) | :::Are you 100% sure? I have yet to see a global variable contradict the expect behaviour. Could you point us to an example mission? [[User:UNN|UNN]] 02:10, 13 September 2007 (CEST) | ||
::::No example mission. Sorry. I just had the experience of using a global var inside one execvm script, and then also calling it from mapclick event and the values wouldn't sync up. When I declared the global in init.sqf then they did sync. I can't quite tell if it's that the global var assignment in one "scope" didn't carry over to the other or what... I'm just saying I noticed something fishy. Maybe I am just mad in the head. :) --[[User:Doolittle|Doolittle]] 05:13, 13 September 2007 (CEST) | |||
Revision as of 05:13, 13 September 2007
Global variables: my advice ... declare them all in init.sqf first!!!!!! Sorry for the yelling but this really really threw me. Global variables held different values when I was just declaring them within scopes of other spawned scripts, etc. and it wasn't obvious what was going on. I'm surprised this isn't even mentioned by anyone.. or is it? --Doolittle 19:49, 12 September 2007 (CEST)
- Did you read this part: Variables#Scope? ++Str 19:58, 12 September 2007 (CEST)
- Yes I did. That's what threw me. "scope does not apply to global variables"... my experience shows it does. --Doolittle 23:24, 12 September 2007 (CEST)
- Are you 100% sure? I have yet to see a global variable contradict the expect behaviour. Could you point us to an example mission? UNN 02:10, 13 September 2007 (CEST)
- No example mission. Sorry. I just had the experience of using a global var inside one execvm script, and then also calling it from mapclick event and the values wouldn't sync up. When I declared the global in init.sqf then they did sync. I can't quite tell if it's that the global var assignment in one "scope" didn't carry over to the other or what... I'm just saying I noticed something fishy. Maybe I am just mad in the head. :) --Doolittle 05:13, 13 September 2007 (CEST)
- Are you 100% sure? I have yet to see a global variable contradict the expect behaviour. Could you point us to an example mission? UNN 02:10, 13 September 2007 (CEST)
- Yes I did. That's what threw me. "scope does not apply to global variables"... my experience shows it does. --Doolittle 23:24, 12 September 2007 (CEST)