C Programming Style 总结
对材料C Programming Style for Engineering Computation的总结。
原文如下:
C Programming Style for Engineering Computation
Created by Aidan Nagorcka-Smith (aidann@student.unimelb.edu.au) //
Definitions and imports
Definitions are in UPPER_CASE
Imports go before definitions
Space between imports, definitions and the main function.
Use definitions for any constants in your program, do not just write them in
Good:
#import <stdio.h>
#import <stdlib.h>
#define MAX_STRING_SIZE 1000
#define DEBUG 0
int main(int argc, char **argv) {
...
Bad:
/* Definitons and imports are mixed up */
#import <stdlib.h>
#define MAX_STING_SIZE 1000
/* Definitions are given names like variables */
#define debug 0
#import <stdio.h>
/* No spacing between imports, definitions and main function*/
int main(int argc, char **argv) {
...
Variables
Give them useful lower_case names
Initialise them to something that makes sense whereever practical.
Good:
int main(int argc, char **argv) {
int i = ;
int num_fifties = ;
int num_twenties = ;
int num_tens = ;
...
Bad:
int main(int argc, char **argv) {
/* Variable not initialised - causes a bug becase we didn't remember to
* set it before the loop */
int i;
/* Variable in all caps - we'll get confused between this and constants */
int NUM_FIFTIES = ;
/* Overly abbreviated variable names make things hard. */
int nt =
while (i < ) {
...
i++;
}
...
Spacing:
Space intelligently, vertically to group blocks of code that are doing a
specific operation, or to separate variable declarations from other code.
One tab of indentation within either a function or a loop.
Spaces after commas.
Space between ) and {
No space between the ** and the argv in the definition of the main function.
Lines at most characters in width
Closing brace goes on its own line
Good:
int main(int argc, char **argv) {
int i = ;
for(i = ; i >= ; i--) {
if (i > ) {
printf("%d bottles of beer, take one down and pass it around,"
" %d bottles of beer.\n", i, i - );
} else {
printf("%d bottles of beer, take one down and pass it around."
" We're empty.\n", i);
}
}
return ;
}
Bad:
/* No space after commas
* Space between the ** and argv in the main function definition
* No space between the ) and { at the start of a function */
int main(int argc,char ** argv){
int i = ;
/* No space between variable declarations and the rest of the function.
* No spaces around the boolean operators */
for(i=;i>=;i--) {
/* No indentation */
if (i > ) {
/* Line too long */
printf("%d bottles of beer, take one down and pass it around, %d bottles of beer.\n", i, i - );
} else {
/* Spacing for no good reason. */
printf("%d bottles of beer, take one down and pass it around."
" We're empty.\n", i);
}
}
/* Closing brace not on its own line */
return ;}
Braces:
Opening braces go on the same line as the loop or function name
Closing braces go on their own line
Closing braces go at the same indentation level as the thing they are
closing
Good:
int main(int argc, char **argv) {
...
for(...) {
...
}
return ;
}
Bad:
int main(int argc, char **argv) {
...
/* Opening brace on a different line to the for loop open */
for(...)
{
...
/* Closing brace at a different indentation to the thing it's closing
*/
}
/* Closing brace not on its own line. */
return ;}
Commenting:
Each program should have a comment explaining what it does and who created it.
Any interesting code should have a comment to explain itself.
We should not comment obvious things - write code that documents itself
Good:
/* change.c
*
* Created by Aidan Nagorcka-Smith (aidann@student.unimelb.edu.au) 13/03/2011
*
* Print the number of each coin that would be needed to make up some change
* that is input by the user
*/
int main(int argc, char **argv) {
int input_change = ;
printf("Please input the value of the change (0-99 cents inclusive):\n");
scanf("%d", &input_change);
printf("\n");
// Valid change values are 0-99 inclusive.
if(input_change < || input_change > ) {
printf("Input not in the range 0-99.\n")
}
...
Bad:
/* No explanation of what the program is doing */
int main(int argc, char **argv) {
/* Commenting obvious things */
/* Create a int variable called input_change to store the input from the
* user. */
int input_change;
...
Code structure:
Fail fast - input checks should happen first, then do the computation.
Structure the code so that all error handling happens in an easy to read
location
Good:
if (input_is_bad) {
printf("Error: Input was not valid. Exiting.\n");
exit(EXIT_FAILURE);
}
/* Do computations here */
...
Bad:
if (input_is_good) {
/* lots of computation here, pushing the else part off the screen. */
...
} else {
fprintf(stderr, "Error: Input was not valid. Exiting.\n");
exit(EXIT_FAILURE);
}
总结:
- 在程序中避免出现Magic Number,使用宏定义(#define)代替,宏定义全部大写。
- 变量在定义时即赋予初值,使用驼峰式(numTens)或_(num_tens)都可以,保持同一种风格。
- 适当使用空格使程序清晰。
- 花空号{}的使用格式,{ 在同一行但有空格,} 单独一行。
- 像是if while for等与后面的 ( 有一个空格。
- 在程序开始前介绍信息(作用、作者等)
- 先检查可能失败项。
C Programming Style 总结的更多相关文章
- [转] 編程風格要素-The Elements of Programming Style 中文英文中英對照
转自: http://www.loliman3000.com/tech/2fe33ce32906f0302412881.php 下面的程序風格規則提煉自Brian Kernighan和P. J. Pl ...
- 【转载】The Elements of Programming Style之代码风格金科玉律
原始日期: 2017-02-06 16:20 <The Elements of Programming Style >是一本很古老的书.尽管 Fortran 我们不太使用,尽管新奇的语言层 ...
- [转] Matlab编程规范(MATLAB Programming Style Guidelines)
转自: Jerry Zitao Liu的博客 主要是参考了下面这篇文章,简洁总结在这里. MATLAB Programming Style Guidelines 简洁总结如下: 表示object的数量 ...
- Java Programming Language Enhancements
引用:Java Programming Language Enhancements Java Programming Language Enhancements Enhancements in Jav ...
- Google Java Style Guide
https://google.github.io/styleguide/javaguide.html Table of Contents 1 Introduction 1.1 Terminolog ...
- Julia is a high-level, high-performance dynamic programming language for technical computing, with syntax that is familiar to users of other technical
http://julialang.org/ julia | source | downloads | docs | blog | community | teaching | publications ...
- The C++ Programming Language - Bjarne Stroustrup
Preface Part 1: Introduction 1.1 The Structure of This Book 1.1.1 Introduction 1.1.2 Basic Facilitie ...
- 类型检查和鸭子类型 Duck typing in computer programming is an application of the duck test 鸭子测试 鸭子类型 指示编译器将类的类型检查安排在运行时而不是编译时 type checking can be specified to occur at run time rather than compile time.
Go所提供的面向对象功能十分简洁,但却兼具了类型检查和鸭子类型两者的有点,这是何等优秀的设计啊! Duck typing in computer programming is an applicati ...
- Flux 普及读本
话说当时做 APP 时,三月不知肉味,再次将眼光投放前端,有种天上一天,地下一年的感觉. Flux 是一种思想 了解的最好方式当然是看Flux官方文档了.React 中文站点也能找到对应的翻译版本,但 ...
随机推荐
- ioc初步理解(一) 简单实用autofac搭建mvc三层+ioc(codeFirst)
1]首先搭好框架 1.1]搭建ui层 1.2]创建其他内库文件 整个项目基本部分搭建完毕之后如下 2]使用nuget引用文件 先在每一个项目中引入ef 然后再UI层引入以下两个文件autofac和Au ...
- WPF 界面如何绑定Command
WPF中,我们使用MVVM,在ViewModel中定义Command和其业务逻辑,界面绑定Command. 那么是不是所有的事件都可以定义Command呢,然后将业务全部放在ViewModel中呢? ...
- MongoDB初了解——用户权限
本文所述MongoDB版本为4.0.5,笔者对MongoDB刚接触,对各个版本的MongoDB不甚了解,本文不对该版本的MongoDB做特性介绍,所涉及命令也许对其余版本不适用. 因为目前有一个试验性 ...
- python多线程爬虫+批量下载斗图啦图片项目(关注、持续更新)
python多线程爬虫项目() 爬取目标:斗图啦(起始url:http://www.doutula.com/photo/list/?page=1) 爬取内容:斗图啦全网图片 使用工具:requests ...
- Shell基础命令(二)
查看Linux的发行版 cat /etc/redhat-release cat /etc/os-release 查看系统用户的id信息 id 用户名 id root id 创建系统用户的命令 user ...
- Android 修改包名,导致安装错误
一.app运行安装时出错 [安装时出错]: [百度翻译] 安装失败的消息未能敲定会议:install_failed_invalid_apk:/数据/应用程序/ vmdl292154713.tmp/9_ ...
- java线程介绍
文章讲解要点 1.线程创建几种方式2.线程常见设置方法,包括优先级.优先级休眠.停止等3.多线程间的数据交互与锁机制4.项目源码下载 线程介绍.png 一.线程创建方式 常见的线程创建方法以下三种 ...
- 【温故而知新】HTTP 报文
HTTP 报文是在 HTTP 应用程序之间发送的数据块.这些数据块以一些文本形式的元信息开头,这些信息描述了报文的内容及含义. 报文流 报文在客户端.服务器和代理之间的流动称为报文流. HTTP 使用 ...
- 【原】Java学习笔记012 - 数组
package cn.temptation; public class Sample01 { public static void main(String[] args) { // 需求:小店对自己的 ...
- MR单元测试以及DeBug调试
Hadoop的MapReduce程序提交到集群环境中运行,出问题时定位非常麻烦,有时需要一遍遍修改代码和打印日志来排查问题,哪怕是比较小的问题.如果数据量很大的话调试起来就相当耗费时间. 而且,Map ...