{"id":43,"date":"2007-05-23T04:01:00","date_gmt":"2007-05-23T11:01:00","guid":{"rendered":"http:\/\/sp2hari.com\/?p=43"},"modified":"2020-06-20T09:04:54","modified_gmt":"2020-06-20T09:04:54","slug":"coding-style","status":"publish","type":"post","link":"https:\/\/sp2hari.com\/index.php\/2007\/05\/23\/coding-style\/","title":{"rendered":"Coding Style …"},"content":{"rendered":"
I have never thought much about coding style before i did my NOSIP<\/a> in Novell<\/a>. But once i started coding for ldtprecord<\/a>, according to the coding style suggested to me by nags<\/a>, i was surprised to see how nice and neat the final code looks.<\/div>\n

Some tips\/tricks for nice coding skills are,<\/p>\n

1. Do spend some time to think about the variable names and the function names. This sometimes might be bit boring, especially when you want to concentrate much on the program logic and performance. But this is Rule 0<\/span> for coding conventions. A variable name “k” can imply anything like “kappa, kozhukattai, katthu, kaadhal, kerala, kozhuppu…” to someone who might have to read your code later. This is again mentioned here<\/a> clearly. Many thanks to emacs, you can always use the auto complete, if your variable name is too long. \ud83d\ude42 .<\/div>\n
2. The actual coding convention depends much on the language and the standards your team is using already. The following style won’t work for someone, whose team is already using a totally different style.<\/div>\n

A few examples for C is posted here .<\/p>\n

Sample Code 1 :<\/span><\/p>\n

if (a == 5) {<\/span>
\n<\/span><\/p>\n

    b = 10;<\/span><\/div>\n

}<\/span>
\nelse {<\/span>
\n    b = 20;<\/span>
\n}<\/span><\/p>\n

Things to be noticed in the above snippet are.<\/p>\n

1. A space between if and “(” .
\n2. Space in both the sides of the comparison operator.
\n3. Space between “)” and “{”
\n4. Space between both the sides of assignment operator (line 2 & 5) . This is true for almost all the operators.
\n5. Proper indentation of lines 2 & 5. If you are using emacs or vi, check here<\/a> for your .emacs or .vimrc file .<\/p>\n

Well, your code will compile and run even if you don’t give these spaces, but a program coded with a bad coding style is equivalent to an inefficient code.<\/div>\n

Sample Code 2<\/span><\/p>\n

Let us have a function which takes two integers and returns their sum .
\nThe code should be like
\n
\nint add_numbers (int num1, int num2) {<\/span>
\n    return (num1 + num2);<\/span>
\n}<\/span><\/p>\n

The function call will be something like,<\/p>\n

int sum;<\/span>
\nsum = add_numbers (10, 20);<\/span><\/p>\n

Things to be noticed in the above snippet is<\/p>\n

In the first line in the function declaration,<\/p>\n

1. The function name should be as clear as possible.
\n2. A space between the end of function name and “(” .
\n3. Spaces are given after every “,” in the function argument list.
\n4. A space is given between “)” and “{“.<\/p>\n

In the second line in the function declaration,<\/p>\n

1. A space before “(“. [ This rule is almost global. Apply it everywhere whenever you use “(” ] .<\/p>\n

2. There is a space on both the sides of the addition operator. This is again almost global. A space between both the sides of operator makes the code look real neat.<\/div>\n

3. The indentation about which was mentioned earlier.<\/p>\n

But yes, if your girl friend is a geek or a nerd or a psycho or a fundoo, then you better go for this. \ud83d\ude09<\/p>\n

#define MAGIC “eilouvy43605321”<\/span>
\n#define _(p,o,q) (t o#p[0])?(q)<\/span>
\n#define __(p,o,q) _(p,o,t-q)<\/span>
\nint main(){int t, i; for(i=8;i>0;i–)printf(“%c”, MAGIC[(((t=(MAGIC+7)[i-1])==’_’)?62:_(.,==,63):_(@,==,64):__(a,>=,’a’+36):__(A,>=,’A’+10):(t-‘0’))]);}<\/span><\/p>\n

Note :: I wont say the coding style i use is the perfect one. It always depends upon what your team was using till now and how easy it is to read, debug and maintain the code.<\/span><\/p>\n

Useful Links :
\n<\/span><\/p>\n

The guide coding standards in GNOME<\/a> is really a nice one.
\nEven better was this one<\/a> i found recently. Though i didn’t read it completely, it was quite interesting.
\nThis<\/a> article was short and sweet.<\/div>\n","protected":false},"excerpt":{"rendered":"

I have never thought much about coding style before i did my NOSIP in Novell. But once i started coding for ldtprecord, according to the coding style suggested to me by nags, i was surprised to see how nice and neat the final code looks. Some tips\/tricks for nice coding …<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[13],"tags":[],"class_list":["post-43","post","type-post","status-publish","format-standard","hentry","category-code"],"_links":{"self":[{"href":"https:\/\/sp2hari.com\/index.php\/wp-json\/wp\/v2\/posts\/43","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sp2hari.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sp2hari.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sp2hari.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/sp2hari.com\/index.php\/wp-json\/wp\/v2\/comments?post=43"}],"version-history":[{"count":2,"href":"https:\/\/sp2hari.com\/index.php\/wp-json\/wp\/v2\/posts\/43\/revisions"}],"predecessor-version":[{"id":1475,"href":"https:\/\/sp2hari.com\/index.php\/wp-json\/wp\/v2\/posts\/43\/revisions\/1475"}],"wp:attachment":[{"href":"https:\/\/sp2hari.com\/index.php\/wp-json\/wp\/v2\/media?parent=43"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sp2hari.com\/index.php\/wp-json\/wp\/v2\/categories?post=43"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sp2hari.com\/index.php\/wp-json\/wp\/v2\/tags?post=43"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}