This is a discussion on Guidelines for Improvement in C programming within the C and C++ forums, part of the Programming Talk category; I have learnt to do some medium to little advanced level C programming. Now I want to refine my learning ...
|
|||||||
|
|||
|
I have learnt to do some medium to little advanced level C programming. Now I want to refine my learning and want to know tips and guidelines a C programmer has to follow to improve their coding style. Can someone give the hints, tips and guidelines a C programmer has to follow so that their code looks good in terms of appearance as well as perform efficiently in terms of
functionality and usage. |
| Sponsored Links |
|
|||
|
There are lot of hints, tips and guidelines a C programmer has to follow so that their code looks good in terms of appearance as well as perform efficiently in terms of functionality and usage. I have given below some of the points which came to my point now.
* In terms of documentation one must take care that there program is intended and documented well with comments written at appropriate places which would help the program for future maintenance. * Prototypes names can be left for future maintenance and usage. * Function names, variable names need to follow naming convention which would help to refer and maintain program easily even for future needs. * If the programmer has need for making use of counters in their c program it is better to take care that counter should not have global scope. |
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Icon Programming Language FAQ | icon-project@cs.arizona.edu | Tech FAQ | 0 | 06-01-2004 04:00 AM |
| Icon Programming Language FAQ | icon-project@cs.arizona.edu | Tech FAQ | 0 | 05-01-2004 04:00 AM |
| comp.lang.eiffel Frequently Asked Questions (FAQ) | Franck Arnaud | Tech FAQ | 0 | 04-17-2004 08:27 AM |
| comp.constraints FAQ (Part 1 of 1) | pse@cs.unh.edu | Tech FAQ | 0 | 04-17-2004 08:23 AM |