global static variables take the precedence over function scoped variables

[Talv]

[9:08 PM] folk: @Talv seems I've located a weird namespacing problem in the galaxy interpreter, where 
int[3] foo;
void bar(int foo) {
    int zed;
    zed = foo;
}
[9:08 PM] folk: will try to assign the outer foo, according to sc2edit, and thus it fails to compile it
[9:09 PM] folk: obviously I've no idea if the actual engine would, or even if the compiler used in sc2edit is the same one or not
[9:10 PM] folk: should be noted that in my actual code both the outer foo and the function are static
[1:34 PM] Talv: yeah, it does seem to happen only when outter variable is static - it seems to take the priority O.o
[1:35 PM] Talv: in this specific case it's not harmful since type miss matches and you get insta error
[1:35 PM] Talv: but I imagine it would be problematic if both parameter and global var would be of the same type
[1:35 PM] Talv: it would compile nicely but you'd get unexpected results ;D

https://discordapp.com/channels/271701880885870594/410894496570671117/548596985268273153

static int[3] foo;
void bar(int foo) {
    int zed;
    zed = foo;
}

error: bulk copy not supported

[BCWhiteStar]

To implement 'static' specifier, an extra field (an integer, just like file descriptor) of variables and functions is set, indicating which file they belong to, while those who are non-static leave it -1. When using an identifier to search symbol table, symbols with fd of the current file will be checked first, then -1 for default symbols.
In this case, static symbols can be selected only if compiler remains in the same file. On the other hand, static symbols really have higher priority.
And it is ok for parameters and variables that hide variables from the outer scope, of course, though they can't be static to make themselves the first symbol to be checked and selected.