RE: C++ basics part 1 09-19-2013, 05:47 AM
#12
No, form is pretty important when you're working with a team of people. If your code is ugly to read, that means its less likely to be read, which tends to lead to bad things.
DOX:
// This function
// will
// return
/* an array if
* it succeeds
*/
// and a null
// pointer
// if it does
// not
Programmer 1: Ain't nobody goin' care bout dis, its just whitespace
Programmer 2: Well fuck that shit, I'll just assume it errors if something goes wrong
<0day effecting the entire world>
Programmer 1: I clearly said it would return a null pointer!
Programmer 2: Fuck you, gumby, why would I read that shit
Very extreme example is extreme.
DOX:
// This function
// will
// return
/* an array if
* it succeeds
*/
// and a null
// pointer
// if it does
// not
Programmer 1: Ain't nobody goin' care bout dis, its just whitespace
Programmer 2: Well fuck that shit, I'll just assume it errors if something goes wrong
<0day effecting the entire world>
Programmer 1: I clearly said it would return a null pointer!
Programmer 2: Fuck you, gumby, why would I read that shit
Very extreme example is extreme.





![[+]](https://sinister.ly/images/modern/collapse_collapsed.png)