Timeline for while(user == gullible)
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 25, 2014 at 18:50 | comment | added | Ingo Bürk | @Tonny Naming is a matter of convention and there are good reasons to not break those conventions without a very good reason. Naming entities against the usual conventions definitely is bad practice – and hence bad code. | |
| Oct 25, 2014 at 18:49 | comment | added | Ingo Bürk | Regarding the variable name, the C standard is actually to use snake_case, so the name should be user_number (and the name itself should be improved). | |
| Oct 25, 2014 at 16:10 | comment | added | Tonny | Capitalizing only classes is just a convention. There is no rule whatsoever against it. Anyway it has nothing to do with optimizing the code. Same goes for your remark about the empty line, but I agree on that one :-) It looks really weird. | |
| Oct 24, 2014 at 18:40 | comment | added | dyp | Please, don't define constants via the preprocessor. We have so many nice alternatives in the compiler's actual language, like const and constexpr. | |
| Oct 24, 2014 at 16:26 | history | answered | Łukasz Rogalski | CC BY-SA 3.0 |