# | User | Rating |
---|---|---|
1 | tourist | 4009 |
2 | jiangly | 3823 |
3 | Benq | 3738 |
4 | Radewoosh | 3633 |
5 | jqdai0815 | 3620 |
6 | orzdevinwang | 3529 |
7 | ecnerwala | 3446 |
8 | Um_nik | 3396 |
9 | ksun48 | 3390 |
10 | gamegame | 3386 |
# | User | Contrib. |
---|---|---|
1 | cry | 167 |
2 | Um_nik | 163 |
3 | maomao90 | 162 |
3 | atcoder_official | 162 |
5 | adamant | 159 |
6 | -is-this-fft- | 158 |
7 | awoo | 156 |
8 | TheScrasse | 154 |
9 | Dominater069 | 153 |
9 | nor | 153 |
Name |
---|
My experience: if you declare a C-style array (like
x
) inside a function, it gets located on your program's stack, however it may not be (and usually isn't) cleaned up. It means you've get an array with some possibly random characters. If you're lucky enough, you'll pass. If not, your program will meet ano
on the border of the board and possibly change the result.Examples: http://ideone.com/CcNtNz — declared inside a function (on the program-specific stack); some garbage inside, you should clean it up.
http://ideone.com/LHg3d5 — outside a function (on the heap); it gets initialized = zeroed.
:) thank you. i didnt know it ..