{"id":694,"date":"2014-06-07T00:01:39","date_gmt":"2014-06-07T07:01:39","guid":{"rendered":"http:\/\/c-for-dummies.com\/blog\/?p=694"},"modified":"2014-08-03T10:05:35","modified_gmt":"2014-08-03T17:05:35","slug":"the-joy-of-clang","status":"publish","type":"post","link":"https:\/\/c-for-dummies.com\/blog\/?p=694","title":{"rendered":"The Joy of Clang"},"content":{"rendered":"

If it were spelled Klang, then it might be a reference some Klingon character from Star Trek<\/em>, but it’s not. Clang is one of those program names that’s a contraction. In this instance, it’s a portmanteau of C Language<\/em>. It’s an \u00fcber nifty command line compiler.
\n
\nIn my most recent C programming book, Beginning Programming with C For Dummies<\/em>, I focus on the IDE method of program creation, specifically by using the Code::Blocks<\/a> environment. That’s pretty much the way all the cool kids are programming today.<\/p>\n

For the small programs introduced in my books, however, the command line works just fine. In fact, if you’re familiar with the command line, it can be easier to use than an IDE for those small programs.<\/p>\n

I use the command line to compose all the sample code in this blog.<\/p><\/blockquote>\n

For years, the cc<\/code> compiler, or the GNU version gcc<\/code>, was preferred for compiling C code. After all, cc<\/code>, was the original C Compiler developed by Kernighan and Ritchie.<\/p>\n

Today, a better solution is clang<\/code>, the C language compiler. Unlike gcc<\/code>, it doesn’t attempt to compile everything, just C code. And it does a super spiffy job.<\/p>\n

On many Unix systems, cc<\/code> is aliased to the clang<\/code> compiler, so using cc<\/code> or clang<\/code> to compile is the same thing.<\/p><\/blockquote>\n

First, a tutorial:<\/p>\n

To compile on the command line, you need a text editor and a compiler\/linker. The routine works like this:<\/p>\n

    \n
  1. Use a text editor to create your code.<\/strong> I use vim<\/code>, the vi improved<\/em> editor, although Unix is bursting at the seams with text editors various and sundry.<\/li>\n
  2. Compile and link the code.<\/strong> The cc<\/code> command is followed by the source code filename. That command both compiles and links, assuming no errors are found.<\/li>\n
  3. Run the program.<\/strong> Type the program’s name at the prompt to see how it works.<\/li>\n<\/ol>\n

    As an example, suppose you wanted to compose the following code:<\/p>\n

    \r\n#include <stdio.h>\r\n\r\nint main()\r\n{\r\n    int x;\r\n\r\n    for(x=65;x<65+26;x++);\r\n        printf(\"%c\",x);\r\n    putchar('\\n');\r\n\r\n    return(0);\r\n}<\/pre>\n
    This code contains a deliberate error — a common programming mistake, but not one that generates a warning when compiled with cc<\/code>. If you can’t find the problem (and most programmers won’t, especially in their own code), then clang<\/code> will.<\/p>\n
    Assume the source code filename is 0607.c<\/code>. The code is compiled with this command:<\/p>\n
    clang 0607.c<\/code><\/pre>\n
    Figure 1 shows a screen cap of the output:<\/p>\n
    \"Figure
    Figure 1. Compiling bugging code by using clang<\/code>.<\/p><\/div>\n
    As you can see, clang<\/code> dutifully spotted the errant semicolon — a bane of all programmers. It specifically pointed out not only the line, but its assumption of what was wrong. Further, it offered a suggestion on how to avoid the warning in the future, should this condition be intentional.<\/p>\n
    Wow.<\/p>\n
    clang<\/code> was developed by Apple and Google several years back, designed to be perfectly compatible with cc<\/code>. If you’re using gcc<\/code> to compile a terminal window, switch to clang<\/code>. You can determine whether or not the system has clang<\/code> installed by typing:<\/p>\n
    clang --version<\/code><\/pre>\n
    at the command prompt.<\/p>\n","protected":false},"excerpt":{"rendered":"
    Forget gcc<\/code>. Banish cc<\/code>. What you need to compile on the command line is clang<\/code>. 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-694","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\/694","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=694"}],"version-history":[{"count":6,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/694\/revisions"}],"predecessor-version":[{"id":930,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/694\/revisions\/930"}],"wp:attachment":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=694"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=694"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=694"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}