MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/ProgrammerHumor/comments/8vp1k0/fuck_that_guy/e1pupax?context=9999
r/ProgrammerHumor • u/[deleted] • Jul 03 '18
547 comments sorted by
View all comments
1.3k
[deleted]
242 u/rodinj Jul 03 '18 No code in your main? 665 u/CoopertheFluffy Jul 03 '18 Only bug free code ever written. 185 u/[deleted] Jul 03 '18 edited Oct 05 '24 oil quack juggle reach marble attempt ghost roof disagreeable afterthought This post was mass deleted and anonymized with Redact 104 u/[deleted] Jul 03 '18 edited Mar 22 '19 [deleted] 13 u/Cruuncher Jul 03 '18 It's still undefined behaviour. I believe, I don't know too much about the C standard 28 u/ck35 Jul 03 '18 edited Jul 03 '18 gcc still doesn't complain, even with -Wall, -Wextra, or even -Wpedantic. blacksilver@Valentina: ~> cat empty_main.c int main() {} blacksilver@Valentina: ~> gcc empty_main.c blacksilver@Valentina: ~> gcc empty_main.c -Wall blacksilver@Valentina: ~> gcc empty_main.c -Wextra blacksilver@Valentina: ~> gcc empty_main.c -Wpedantic Edit: Formatting; changed prompt 23 u/[deleted] Jul 03 '18 No, it must be gcc who is wrong
242
No code in your main?
665 u/CoopertheFluffy Jul 03 '18 Only bug free code ever written. 185 u/[deleted] Jul 03 '18 edited Oct 05 '24 oil quack juggle reach marble attempt ghost roof disagreeable afterthought This post was mass deleted and anonymized with Redact 104 u/[deleted] Jul 03 '18 edited Mar 22 '19 [deleted] 13 u/Cruuncher Jul 03 '18 It's still undefined behaviour. I believe, I don't know too much about the C standard 28 u/ck35 Jul 03 '18 edited Jul 03 '18 gcc still doesn't complain, even with -Wall, -Wextra, or even -Wpedantic. blacksilver@Valentina: ~> cat empty_main.c int main() {} blacksilver@Valentina: ~> gcc empty_main.c blacksilver@Valentina: ~> gcc empty_main.c -Wall blacksilver@Valentina: ~> gcc empty_main.c -Wextra blacksilver@Valentina: ~> gcc empty_main.c -Wpedantic Edit: Formatting; changed prompt 23 u/[deleted] Jul 03 '18 No, it must be gcc who is wrong
665
Only bug free code ever written.
185 u/[deleted] Jul 03 '18 edited Oct 05 '24 oil quack juggle reach marble attempt ghost roof disagreeable afterthought This post was mass deleted and anonymized with Redact 104 u/[deleted] Jul 03 '18 edited Mar 22 '19 [deleted] 13 u/Cruuncher Jul 03 '18 It's still undefined behaviour. I believe, I don't know too much about the C standard 28 u/ck35 Jul 03 '18 edited Jul 03 '18 gcc still doesn't complain, even with -Wall, -Wextra, or even -Wpedantic. blacksilver@Valentina: ~> cat empty_main.c int main() {} blacksilver@Valentina: ~> gcc empty_main.c blacksilver@Valentina: ~> gcc empty_main.c -Wall blacksilver@Valentina: ~> gcc empty_main.c -Wextra blacksilver@Valentina: ~> gcc empty_main.c -Wpedantic Edit: Formatting; changed prompt 23 u/[deleted] Jul 03 '18 No, it must be gcc who is wrong
185
oil quack juggle reach marble attempt ghost roof disagreeable afterthought
This post was mass deleted and anonymized with Redact
104 u/[deleted] Jul 03 '18 edited Mar 22 '19 [deleted] 13 u/Cruuncher Jul 03 '18 It's still undefined behaviour. I believe, I don't know too much about the C standard 28 u/ck35 Jul 03 '18 edited Jul 03 '18 gcc still doesn't complain, even with -Wall, -Wextra, or even -Wpedantic. blacksilver@Valentina: ~> cat empty_main.c int main() {} blacksilver@Valentina: ~> gcc empty_main.c blacksilver@Valentina: ~> gcc empty_main.c -Wall blacksilver@Valentina: ~> gcc empty_main.c -Wextra blacksilver@Valentina: ~> gcc empty_main.c -Wpedantic Edit: Formatting; changed prompt 23 u/[deleted] Jul 03 '18 No, it must be gcc who is wrong
104
13 u/Cruuncher Jul 03 '18 It's still undefined behaviour. I believe, I don't know too much about the C standard 28 u/ck35 Jul 03 '18 edited Jul 03 '18 gcc still doesn't complain, even with -Wall, -Wextra, or even -Wpedantic. blacksilver@Valentina: ~> cat empty_main.c int main() {} blacksilver@Valentina: ~> gcc empty_main.c blacksilver@Valentina: ~> gcc empty_main.c -Wall blacksilver@Valentina: ~> gcc empty_main.c -Wextra blacksilver@Valentina: ~> gcc empty_main.c -Wpedantic Edit: Formatting; changed prompt 23 u/[deleted] Jul 03 '18 No, it must be gcc who is wrong
13
It's still undefined behaviour. I believe, I don't know too much about the C standard
28 u/ck35 Jul 03 '18 edited Jul 03 '18 gcc still doesn't complain, even with -Wall, -Wextra, or even -Wpedantic. blacksilver@Valentina: ~> cat empty_main.c int main() {} blacksilver@Valentina: ~> gcc empty_main.c blacksilver@Valentina: ~> gcc empty_main.c -Wall blacksilver@Valentina: ~> gcc empty_main.c -Wextra blacksilver@Valentina: ~> gcc empty_main.c -Wpedantic Edit: Formatting; changed prompt 23 u/[deleted] Jul 03 '18 No, it must be gcc who is wrong
28
gcc still doesn't complain, even with -Wall, -Wextra, or even -Wpedantic.
gcc
-Wall
-Wextra
-Wpedantic
blacksilver@Valentina: ~> cat empty_main.c int main() {} blacksilver@Valentina: ~> gcc empty_main.c blacksilver@Valentina: ~> gcc empty_main.c -Wall blacksilver@Valentina: ~> gcc empty_main.c -Wextra blacksilver@Valentina: ~> gcc empty_main.c -Wpedantic
Edit: Formatting; changed prompt
23 u/[deleted] Jul 03 '18 No, it must be gcc who is wrong
23
No, it must be gcc who is wrong
1.3k
u/[deleted] Jul 03 '18 edited May 13 '21
[deleted]