{"id":7156,"date":"2025-09-20T00:01:00","date_gmt":"2025-09-20T07:01:00","guid":{"rendered":"https:\/\/c-for-dummies.com\/blog\/?p=7156"},"modified":"2025-09-13T10:53:16","modified_gmt":"2025-09-13T17:53:16","slug":"finding-those-pesky-null-characters","status":"publish","type":"post","link":"https:\/\/c-for-dummies.com\/blog\/?p=7156","title":{"rendered":"Finding Those Pesky Null Characters!"},"content":{"rendered":"

You’ve crafted a brilliant function, ensuring that it properly processes words and generates needed output. Is the code perfect? Well, it looks perfect. But how do you know for certain?
\n
\nThe following program outputs the word pneumonoultramicroscopicsilicovolcanoconiosis, reportedly the longest word in the English language. It uses a clever while<\/em> statement where the condition is neatly obfuscated — something I avoid doing in my own code.<\/p>\n

2025_09_20-Lesson.c<\/a><\/h3>\n
\r\n#include <stdio.h>\r\n\r\nint main()\r\n{\r\n    char word[] = \"pneumonoultramicroscopicsilicovolcanoconiosis\";\r\n    int x = 0;\r\n\r\n    while( putchar( word[x++] ) )\r\n        ;\r\n    putchar('\\n');\r\n\r\n    return 0;\r\n}<\/pre>\n
Here is the output, exactly as planned — or is it?<\/p>\n
pneumonoultramicroscopicsilicovolcanoconiosis<\/code><\/p>\n
Well, you know that the output doesn’t appear exactly as planned or I wouldn’t have asked the question. The point is that I’ve often written code where the output looks great, but upon closer examination flaws in the code go unnoticed. Especially with text output, it’s easy to overlook things you cannot see, specifically null characters that are part of output but do not print. For the code above, this extra output is exactly what happens.<\/p>\n
This month’s Exercise<\/a> provides a good example. One of my first solutions looked great! But when I examined the output more closely, it was pockmarked with null characters.<\/p>\n
One way to check whether the program’s output is proper is to run it through the hexdump<\/em> filter, a Linux command line utility. For example:<\/p>\n
$ .\/a.out | hexdump -C<\/code><\/p>\n
The program’s name is a.out<\/code>, the default. It’s prefixed with .\/<\/code>, which directs the command interpreter to look for and run the file found in the current directory. The -C<\/code> switch directs the hexdump<\/em> utility to use the Canonical format, which includes the ASCII portion (the third column). Here is the command’s output.<\/p>\n
00000000  70 6e 65 75 6d 6f 6e 6f  75 6c 74 72 61 6d 69 63  |pneumonoultramic|
\n00000010  72 6f 73 63 6f 70 69 63  73 69 6c 69 63 6f 76 6f  |roscopicsilicovo|
\n00000020  6c 63 61 6e 6f 63 6f 6e  69 6f 73 69 73 00<\/span> 0a     |lcanoconiosis..|
\n0000002f<\/code><\/p>\n
Pay attention to the last word of output. Byte 0x73 is the final ‘s’ in pneumonoultramicroscopicsilicovolcanoconiosis. Then comes a null character, 0x00, then finally the newline 0x0a. The null character doesn’t print, so you don’t see it in the output &mdash but it’s there!<\/p>\n
When you code a program that outputs text, always double-check the output to confirm that it’s free from unwanted null characters. For this month’s Exercise, an early solution looked good, but it was polka dotted with null characters. I noticed the flaw in my logic, and fixed the code to prevent the null characters from appearing.<\/p>\n
I can think of a number of ways to fix the sample code, most of which involve deconstructing the while<\/em> loop’s clever condition. This alternative works:<\/p>\n
while( word[x] )
\n    putchar(word[x++]);<\/code><\/p>\n
These statements show the while<\/em> loop as just two lines, which retains the incrementing operator inside the brackets. My preferred way to write this code is to set the x++<\/code> as its own statement, which is more readable, but whatever.<\/p>\n
Any way you code it, always confirm that the output is free from null characters. Yes, you may not see them, and users wouldn’t notice them, but they may have unintentional consequences for non-obvious uses of the program.<\/p>\n","protected":false},"excerpt":{"rendered":"
Do you think that your code is perfect? Run it through hexdump<\/em> and guess again! Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-7156","post","type-post","status-publish","format-standard","hentry","category-main"],"_links":{"self":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/7156","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=7156"}],"version-history":[{"count":5,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/7156\/revisions"}],"predecessor-version":[{"id":7168,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/7156\/revisions\/7168"}],"wp:attachment":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=7156"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=7156"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=7156"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}