Here is why one should be very careful while mixing signed and unsigned integer comparisons. Take a look at this code snippet below:<\/p>\n
#include <iostream>\r\n#include <string>\r\n\r\nint main(int argc, char *argv[])\r\n{\r\n std::string presidentsOrders = \"NO lets do more sanctions\";\r\n unsigned int pos;\r\n\r\n pos = presidentsOrders.find(\"YES\");\r\n if (pos != std::string::npos) {\r\n std::cout << \"Lets nuke North Korea\" << std::endl;\r\n } else {\r\n std::cout << \"More sanctions (yawn)\" << std::endl;\r\n }\r\n return 0;\r\n}<\/pre>\nThe President does not want to nuke North Korea, but lets see how the program actually interprets this. If you try compiling and executing this program in a 32-bit environment, it will work as it should:<\/p>\n
abhi@devserver:~\/cpp_string_pos$ .\/a.out \r\nMore sanctions (yawn)\r\nabhi@devserver:~\/cpp_string_pos$\r\n<\/pre>\nNow compile the same program in a 64-bit environment (you can cross-compile using the -m32 or -m64 flag in g++). Here is the result:<\/p>\n
abhi@devserver:~\/cpp_string_pos$ g++ cpp_string_pos32.cpp -m64\r\nabhi@devserver:~\/cpp_string_pos$ .\/a.out \r\nLets nuke North Korea\r\nabhi@devserver:~\/cpp_string_pos$<\/pre>\nSo we effectively misinterpreted the order to fire the nuclear missile. The problem is that std::string::npos is a size_t type and usually defined as:<\/p>\n
\r\nstatic const size_t npos = -1;\r\n<\/pre>\nThis is 0xFFFFFFFF <\/code> on 32-bit, but becomes 0xFFFFFFFFFFFFFFFF<\/code> on 64-bit. The comparison on 64-bit is then between the unsigned int pos which is upconverted to 0x00000000FFFFFFFF<\/code> and 0xFFFFFFFFFFFFFFFF<\/code> causing the check to fail and the nuke getting fired. So the right thing to do here is to use std::string::size_type for pos<\/code> instead which would store the right value in the pos<\/code> variable. This is of course an exaggerated example, and I do hope that missile systems have more levels of strict checks that need to be cleared before they get fired, but it showcases how disastrous this kind of mistake can be. Poor choices of data types for variables can really run your program into the ground.<\/p>\n","protected":false},"excerpt":{"rendered":"Here is why one should be very careful while mixing signed and unsigned integer comparisons. Take a look at this code snippet below: #include <iostream> #include <string> int main(int argc, char *argv[]) { std::string presidentsOrders = “NO lets do more sanctions”; unsigned int pos; pos = presidentsOrders.find(“YES”); if (pos != std::string::npos) { std::cout << “Lets … [Read more…]<\/a><\/span><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/www.asrivas.me\/blog\/wp-json\/wp\/v2\/posts\/203"}],"collection":[{"href":"https:\/\/www.asrivas.me\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.asrivas.me\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.asrivas.me\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.asrivas.me\/blog\/wp-json\/wp\/v2\/comments?post=203"}],"version-history":[{"count":7,"href":"https:\/\/www.asrivas.me\/blog\/wp-json\/wp\/v2\/posts\/203\/revisions"}],"predecessor-version":[{"id":215,"href":"https:\/\/www.asrivas.me\/blog\/wp-json\/wp\/v2\/posts\/203\/revisions\/215"}],"wp:attachment":[{"href":"https:\/\/www.asrivas.me\/blog\/wp-json\/wp\/v2\/media?parent=203"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.asrivas.me\/blog\/wp-json\/wp\/v2\/categories?post=203"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.asrivas.me\/blog\/wp-json\/wp\/v2\/tags?post=203"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}