I wonder why so many high-rated users do not use short FOR-loop in c++. I think that there are many benefits like better readability of code and it also saves time. So, why don't users like tourist use it?
# | 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 | 164 |
1 | maomao90 | 164 |
3 | Um_nik | 163 |
4 | atcoder_official | 160 |
5 | -is-this-fft- | 158 |
6 | adamant | 157 |
6 | awoo | 157 |
8 | TheScrasse | 154 |
8 | nor | 154 |
10 | djm03178 | 153 |
I wonder why so many high-rated users do not use short FOR-loop in c++. I think that there are many benefits like better readability of code and it also saves time. So, why don't users like tourist use it?
Name |
---|
I personally would disagree that it gives better readability.
Also, C macros were not designed for such purposes.
The reason is simply writability (fewer keystrokes).
One of the main problems of C/C++ contest macros is that everyone has their own set of macros, so writes in their own unique language. You may be fine with that as a lone contestant who never reads other contestants' code (no team contests, no hacking attempts, no problemsetting, etc.). But as you reach out to these and other areas, you find yourself reading other programmers' code quite often, and learning a new set of macros every time is just not worth it.
Another problem is applicability of macros: different versions have different domains, and with a particularly unsafe tool such as macros, stepping outside the domain usually results in a silent error. Considering the time one has to spend to debug a C preprocessor macro, the usability gain of macros is questionable.