I just moved to a new computer. The process involved taking all my personal programs and re-compiling them for the new system. It took a while, but fortunately everything works with my various programs doing their necessary jobs. That is, unless I see a weirdo error upon compiling one of those golden oldies. On such error I saw made me wonder what they heck I was doing in my code.
\n
\nHere is the error I witnessed when I compiled one of my handy utility programs:<\/p>\n
The program runs, of course. I’ve been using it for years. And the warning message is easily addressed by adding another set of parentheses:<\/p>\n Still, this construction is weird. What the heck does it do? What was I<\/em> trying to do when I coded the thing. Honestly, I have no idea.<\/p>\n Further, this expression (or a similar one) appears seven times in the code. It’s not a mistake; I don’t mean to compare the values in the two pointers. No, it’s an assignment. The loop keeps repeating until the value assigned is the null character or zero. My guess is that I’m building a string, but the problem is that the code utterly lacks comments.<\/p>\n Yes, it’s typical of me to quickly cobbled together a utility and not bother to comment anything. Of the 300-plus lines of code in the file, nary a comment is to be found. I know what the program does, but even the variables are poorly named: To seek to better understand what the expression accomplishes, I decided to write a separate program to put the while<\/em> loop to work. Here is what I came up with:<\/p>\n Storage is allocated for pointer Here’s the output:<\/p>\n This small program demonstrated what I thought was going on with the weirdo while<\/em> loop: It duplicates a string. More specifically, the code builds a string, adding characters to a buffer Fast forward ten years to the time I must re-compile the code and — ta-da!<\/em> — confusion reigns. Yet another good lesson in why it’s important to comment your code, even the silly stuff you write for yourself.<\/p>\n","protected":false},"excerpt":{"rendered":" A good lesson in why you should comment your code, even the stuff you write for yourself. Continue reading warning: using the result of an assignment as a condition without parentheses [-Wparentheses]
\n while((*a++) = (*c++))
\n ~~~~~~~^~~~~~~~<\/code><\/p>\nwhile( ((*a++) = (*b++)) )
\n ;<\/code><\/p>\na<\/code> and b<\/code>?. For me, as someone who teaches C programming and should know better, this situation is very frustrating.<\/p>\n2023_04_29-Lesson.c<\/a><\/h3>\n
\r\n#include <stdio.h>\r\n#include <stdlib.h>\r\n#include <string.h>\r\n\r\nint main()\r\n{\r\n char *sto,*a;\r\n const char *b = \"string\\n\";\r\n\r\n sto = malloc( sizeof(char)*strlen(b) + 1 );\r\n\r\n a = sto;\r\n while( ((*a++) = (*b++)) )\r\n ;\r\n\r\n printf(\"%s\",sto);\r\n\r\n return(0);\r\n}<\/pre>\nsto<\/code>, enough to store the string referenced by constant b<\/code>. Pointer a<\/code> is a reference. Once it’s initialized to the address of sto<\/code>, the while<\/em> loop copies characters from b<\/code> to a<\/code>. The loop repeats until the null character is copied, which makes the expression FALSE. The string is copied and the loop stops.<\/p>\nstring<\/code><\/p>\na<\/code> from other sources referenced by pointer b<\/code>. It would have been so much easier to just jot that information down in a comment. But no. I was probably in a hurry doing what I refer to as a “brain dump.”<\/p>\n