ForEach Help

[- VJ -]

Can i get some help with a this bit of code.

 

Say I have.

 

_ver1 = x;

_ver2 = y;

_ver3 = z;

_ver4 = 1;

_ver5 = 2;

 

{some code}forEach[_ver1,_ver2,_ver3,_ver4,_ver5] // <--- Rather than having to type out all the _ver,  is there a way to set it up like

 

{some code}forEach[_ver%1, _x] // <-- like so

 

I hope someone understands what a am asking and if it is possible.

 

Thanks

 

- VJ - 

[DirtySanchez]

Can i get some help with a this bit of code.

Say i have.

_ver1 =

_ver2

_ver3

_ver4

_ver5

Well um it's an interesting idea!

No, did you not give much information on purpose or are we suppose to work with just that to help you?

[- VJ -]

Well um it's an interesting idea!

No, did you not give much information on purpose or are we suppose to work with just that to help you?

 

lol accidentally posted to early but finished and reposted.

[Halvhjearne]

not sure why you would want the variables to change (since it usually means a major security flaw) and im not sure if its even possible with a private variable.

 

why not use the first example? i dont see the problem in that.

[- VJ -]

not sure why you would want the variables to change (since it usually means a major security flaw) and im not sure if its even possible with a private variable.

 

why not use the first example? i dont see the problem in that.

I dont want to change the variable i want to cycle through them in the forEach "loop" instead of typing each one out.

 

and too much extra code.

[Halvhjearne]

I dont want to change the variable i want to cycle through them in the forEach "loop" instead of typing each one out.

 

and too much extra code.

 

well you would basicly be changing the variable from what you are explaining ... either way you should just use the first example for security reasons, especially if there is no reason to do it otherwise.

 

if you want to streamline/optimize your code, you should wait and do it when you are done writing the script, there is no such thing as too much code, however optimizations can usually be done when functionallity is complete.

 

if there is a specific reason for you to do it this way, you will have to explain this, else nobody can really help you.

[- VJ -]

OK so can you explain the security risk of doing this.

[Halvhjearne]

OK so can you explain the security risk of doing this.

 

1. you cant whitelist a variable that you do not know the name of before using it
2. global variables can be easily changed
3. if allowing all random variables hacking will be extremely easy

you should always use easily reconizable variables that can be whitelisted if needed, using random or changing variables should be kept on the server if needed at all.

 

in the case you show, the best way to streamline it would prob be something like this:

_vers = [x,y,z,1,2];

{some code}forEach _vers;

[- VJ -]

lol ok im not being clear. I want to I have _VERx (x = a number) I would like to auto increase each turn or will this work

 

_vers = [[x,y],[z,1],[2,3]];

{some code}forEach _vers;

 

and if so would i call them like

 

{

_value1 =  ((_x select 0) select 0);

_value2 =  ((_x select 0) select 1);

}forEach _vers;

[- VJ -]

p.s Thanks for the help so far.

[Halvhjearne]

lol ok im not being clear. I want to I have _VERx (x = a number) I would like to auto increase each turn or will this work

 

_vers = [[x,y],[z,1],[2,3]];

{some code}forEach _vers;

 

and if so would i call them like

 

{

_value1 =  ((_x select 0) select 0);

_value2 =  ((_x select 0) select 1);

}forEach _vers;

 

im still unsure what you are trying to do with this, but it seems fine to me like this ...

[- VJ -]

:-) Thank you.

[raymix]

Plenty of ways, sky's the limit. There's generally 4 ways to declare variable, one you know - by simply doing it, i'll show you 2 more, but fourth one i'll keep to myself for reasons.

 

Now then:

_arr = ["x","y","z",1,2,3];

for "_i" from 0 to (count _arr -1) do {
	missionNamespace setVariable [(format["value%1",_i]),_arr select _i]; //value1 = x, value2 = y etc...
};

{
	missionNamespace setVariable [(format["value%1",_forEachIndex]),_arr select _forEachIndex]; //value1 = x, value2 = y etc...
} forEach _arr; 

_cnt = -1;
{
	_cnt = _cnt +1;
	missionNamespace setVariable [(format["value%1",_cnt]),_x]; //value1 = x, value2 = y etc...
} count _arr; 

_cnt = -1;
{
	_cnt = _cnt +1;
	call compile format ["_var%1 = %2",_cnt,_x]; //_var1 = x, _var2 = y etc...
} count _arr;

The last part is an interesting one, what it does is creates a string, then converts it into {code} using compile, then removes these code brackets by calling it. This in return allows you to declare local vars ofc.

[Halvhjearne]

this is making it more complicated, not to mention less secure than needed ... i doubt you can even use the last part for anything as the private variable will be nil outside that scope.

[- VJ -]

it ok got it all working thanks for your info though