Oracle Being Oracle

Content 11:05 AM ... 0.01Ks all Fido 3G Emergency calls only 51 X rShowerthoughts uScriptman777 9h Programming is like magic in fantasy, you start with simple spells and slowly learn how to create more and more complex and powerful ones. Some mages use this power for the good of people, some don't. 1.5k J 94 Share BEST COMMENTS hollowstriker 7h And when it works or didn't, we don't know why. Reply 193 TrancaDorada 4h And i always hear dumbledore in my head : "Just trust in magic, Harry". : Reply 2 more replies 44 Add a comment

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

Content awayjester199902 6h why do you put 2 equal signs? 2 J the-eclectic-chair 6h In a lot of programming languages, 1 equal sign assigns values to keywords, like 10. However, 2 equal signs makes a comparison. So 1 1 will return True while 1 2 will return False. 17 J icneto 2h And then you have JavaScript with to make sure that your elephant is not an orange. 5 J

Content EVE SEEN THINGS YOU PEOPLE WOULDN'T BELIEVE. GLOBAL VARIABLES HIDDEN IN THE DARKEST FILES. HTML TABLES AND INLINE FLOAT STYLES STORED IN SQL STRINGS..... ALL THOSE BUGS WILL BE LOST IN TIME, LIKE PROJECTS MADE BY GOOGLE. imaflio.com

You've spent weeks writing pristine code, achieved that mythical 100% test coverage, handled every edge case known to humanity... and then some user decides to put 🎉💀🔥 in the name field. Your entire validation layer just got obliterated by three Unicode characters. Because apparently, while you were busy testing for SQL injection and XSS attacks, nobody thought to ask "what if someone just... doesn't use letters?" Your regex that confidently checks for ^[a-zA-Z]+$ is now weeping in the corner while your database tries to figure out how to sort "John Smith" and "💩". Fun fact: Emojis are stored as multi-byte UTF-8 characters, which means your VARCHAR(50) field might actually only fit like 12 emojis. But sure, your tests passed. Your beautiful, emoji-less tests.

You ask SQL for something simple like "give me the first 100 users" and it responds by VIOLENTLY LAUNCHING YOU INTO THE STRATOSPHERE like you just insulted its entire family tree. SQL doesn't do "gentle" or "proportional responses" – it's either giving you exactly what you want with surgical precision OR it's yeeting your entire production database into the void because you forgot a semicolon. There's literally no in-between. One tiny query and suddenly you're SpongeBob getting absolutely OBLITERATED by Patrick's raw, unfiltered power. The drama! The chaos! The sheer unnecessary force of it all!