Your Outie Writes Unit Tests

Content Java NOO00000000!!!! YOU CANT USE POINTERS THEY ARE DANGEROUS AND PRODUCE MANY BUGS!!!!!! haha int p goes brrrrrrr

Content Hey, So Did You Fix That Bug? Yes 158531 DAL E

You know that euphoric moment when you finally solve that bug that's been haunting you for 6 hours, close Stack Overflow tab #47, MDN docs tab #82, GitHub issues tab #93, and approximately 78 other "javascript why does this not work" Google searches? That's the zen state depicted here. The browser tab hoarding is real - we open tabs faster than we can say "let me just check one thing real quick." Each tab represents a rabbit hole of documentation, Stack Overflow threads, and that one blog post from 2014 that might have the answer. Closing them all after shipping your feature hits different than meditation ever could.

Content Have you ever seen code so bad it made you laugh? David Seidman, former Security Program Manager at Microsoft (2005-2016) Answered Feb 8 Upvoted by Aveesha Sharma, Masters of Science Software Engineering, Arizona State Univ... and Mandeep Kaur, MS Software Engineering, San Jose State University (2017) R. I was working for Microsoft's security incident response team investigating a vulnerability. We opened up the relevant file. It contained 10,000 lines of uncommented archaic C code. At the top was a single comment: This code has bugs. It did. ProdrammerHumor.io

Content uAutoModerator Friar Me trying to fix syntax errors in my comment before it gets deleted made with mematic ProarammerHumor.io

Content Ijust wanted to add to this discussion that I am just compiling on VS and GCC, and used to use include guards. I have now switched to pragma once, and the only reason for me is not 199 performance or portability or standard as I don't really care what is standard as long as VS and GCC support it, and that is that: pragma once reduces possibilities for bugs. It is all too easy to copy and paste a header file to another header file, modify it to suit ones needs, and forget to change the name of the include guard. Once both are included, it takes you a while to track down the error, as the error messages arent necessarily clear. Share Follow edited Nov 30, 2014 at 9:57 answered Jul 22, 2011 at 16:55 Cookie 11.7k 13 52 81 5 This is the correct reason. Forget performance--we should use pragma once because it's less error prone. It occurs to me that if compilers are already tracking include guards, they're already doing most of the work necessary to issue warnings when they see different files using the same macro name. - rieux Jun 13, 2019 at 6:36 Add a comment pragma once has unfixable bugs. It should never be used. 169 If your include search path is sufficiently complicated, the compiler may be unable to tell the difference between two headers with the same basename (e.g. afoo.h and bfoo.h), so a pragma once in one of them will suppress both. It may also be unable to tell that two different relative includes (e.g. include "foo.h" and include "..afoo.h" refer to the same file, so pragma once will fail to suppress a redundant include when it should have. lanc arca attocic tho commorc amia