An array function in Irrlicht

I'm trying to run a function which uses a 2d array as a parameter, and it's giving me shit most of the time.

Explicitly, I'm using Irrlicht's 2d graphicsdemo (#6), I create a 2d array of int *myarray[4][4];, my function is:

    void initmyarray(int *thisarray[4][4])
    {
        int x, y = 0;
    for(x=0;x < 5; ++x)
    {for(y=0; y < 5;++y )
        {
            thisarray[x][y] = 0;
        }
    };
    };

I run the declaration (or whatever) and function as initmyarray(myarray2); before the while(device->run() && driver) runs, and after     driver->getMaterial2D().AntiAliasing=video::EAAM_FULL_BASIC; runs, and although I can finally get the program to compile, and it makes the animated imps blink after each loop. I tried renaming initarry and myarray obviously, but after trying to pass arguments and shit properly this happens. If I comment out initmyarray(myarray2); the imps animate properly.



Suggestions? I'll use vectors if I have to, I'm just trying to make a 2d grid with which I can do shit.

I'm running Code::Blocks with MingW, and the only build option is produce debugging symbols.

>>6
The last dimension of an array is necessary when passing a multidimensional array as a function, I just through in the other dimension so I wouldn't have to worry if C++ was fucking around with something I didn't know.

Turns out another bug shows up: I made a function to print my array, and I think I found out at least part of why the imps fuck up. The first three dimensions of imp2 enter my array at some point at the last three memory locations (5, 3-5), if the array is initialized before the imp rectangles are made. Afterwards probably interferes with the imp memory or something which is why it takes a shit. I'm filing a report with Sourceforge tomorrow because that shit is dumb.