blocks|key|3309723|text|您可以通过将函数或对象声明为"static“来使其作用域位于其源文件的本地。这有点帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3309724|否则，我看到的避免名称空间冲突的典型习惯用法是在名称上添加某种工具标识符。例如，foo.c中的所有内容都可以命名为foo_*|3309725|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

<p>You can make a function or object's scope local to its source file by declaring it "static". That helps a bit.</p>

<p>Otherwise, the typical idiom I see for avoiding namespace clashes is to put some kind of facility identifier onto the name. For instance, everything in foo.c might be named foo_*</p>


blocks|key|331957|text|老实说，我不认为StackOverflow上的许多答案会教你如何设计和编写结构良好的C程序。你需要读一本好书，最明显的一本书是Kernighan+&+Ritchie的The+C+Programming+Language。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|331958|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/The_C_Programming_Language_%2528book%2529^0|2B|Q|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

<p>I honestly don't think that any number of answers on StackOverflow 
are going to teach you how to design and write well-structured C programs. You need to read a good book, and the obvious one to read is <a href="http://en.wikipedia.org/wiki/The_C_Programming_Language_%28book%29" rel="noreferrer">The C Programming Language</a> by Kernighan &amp; Ritchie.</p>


blocks|key|333502|text|和其他优秀的C程序员一起工作，会和他们一起进行代码审查。不仅让他们看你的代码，你还要看他们的代码。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|333503|entityMap^0|0|F|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

<p><strong>Work with other good C programmers.</strong>  Have a code review with them.  Not only let them look at your code, but you look at their code.</p>


blocks|key|337001|text|您可以用纯C语言进行面向对象的设计。一种简单的方法是将模块看作是一个具有公共方法的class，就像需要this参数作为显式第一个参数的普通函数一样。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|337002|如果class名称是函数名称的前缀，并且所有私有函数和类数据都声明为static，则会有所帮助。您可以使用malloc()构建构造函数来获取内存和数据字段的显式初始化。|337003|具有完全私有数据成员的对象的构造函数可以公开不透明的指针(甚至是类型化的void+*，如果需要类型安全，也可以作为指向不完整类型的指针)。如果您只想拥有公共数据成员，那么指向公共定义的struct的指针效果很好。|337004|遵循此模式的还有许多库。初始化函数返回一个cookie，该cookie必须传递回所有的库方法，其中一个方法充当析构函数。|337005|当然，在纯C中还有其他方法可以很好地设计，但如果OO对您有效，那么您不必完全放弃它。|337006|entityMap^0|15|5|1F|4|0|2|5|Y|6|1H|8|0|10|6|2K|6|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|11|8|@$9|12|A|13|B|C]|$9|14|A|15|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|16|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|17|8|@]|D|@]|E|$]]|$1|N|3|-4|5|6|7|18|8|@]|D|@]|E|$]]]|O|$]]

<p>You can do object oriented design in pure C.  An easy approach is to think of a module as a <code>class</code> with public methods as ordinary functions that require the <code>this</code> parameter as an explicit first argument.</p>

<p>It helps if the <code>class</code> name is a prefix on the function name, and if all private functions and class data are declared <code>static</code>. You build constructors with <code>malloc()</code> to get the memory, and explicit initialization of the data fields.</p>

<p>A constructor for an object with entirely private data members can expose an opaque pointer (typed <code>void *</code> even, or as a pointer to an incomplete type if type safety is desired). If you want to have only public data members, then a pointer to a publicly defined <code>struct</code> works well.</p>

<p>This pattern is followed by a number of libraries. An initialization function returns a cookie that must be passed back to all library methods, and one method serves as a destructor.</p>

<p>Of course, there are other ways to design well in pure C, but if OO works for you, you don't have to abandon it completely.</p>


blocks|key|333509|text|您可以将文件范围内的变量和函数的可见性限制为它们各自的源文件(尽管这不会阻止您传递指向这些对象的指针)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|333510|例如：|333511|/**+foo.c+*/
static+void+foo_helper()+{...}+/*+foo_helper+cannot+be+called+by+name+
++++++++++++++++++++++++++++++++++outside+of+foo.c+*/
static+int+local_state;++++++++/*+local+state+is+visible+at+file+scope,
++++++++++++++++++++++++++++++++++but+is+not+exported+to+the+linker+*/|code-block|syntax|javascript|333512|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

<p>You can restrict visibility of file-scope variables and functions to their respective source files (although that doesn't prevent you from passing pointers to these objects around).</p>

<p>For example:</p>

<pre><code>/** foo.c */
static void foo_helper() {...} /* foo_helper cannot be called by name 
                                  outside of foo.c */
static int local_state;        /* local state is visible at file scope,
                                  but is not exported to the linker */
</code></pre>


blocks|key|333553|text|好消息是，你可以在C中以半面向对象的方式编程。你可以保护数据，公开访问函数，等等。它可能没有C%2B%2B的所有奇妙之处，但从我看到的其他人的C%2B%2B代码来看，许多人无论如何都不使用这种奇妙之处。换句话说，人们在类中编写C代码，而在C中，您可以在没有类容器的情况下编写相同的代码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|333554|首先，读一本关于C编程和风格的书，K&R很好。其次，我建议你去看看CERT+Programming+Standard。尽管这个站点主要关注“安全”编码标准，但这里的大部分内容都是每个人都应该遵循的通用代码质量标准。做这里提到的事情将提高你的质量，消除讨厌的bug，并且作为一个副作用，使你的代码更安全。|offset|length|333555|entityMap|0|LINK|mutability|MUTABLE|url|https://www.securecoding.cert.org/confluence/display/seccode/CERT%2BC%2BSecure%2BCoding%2BStandard^0|0|X|P|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

<p>Good news is that you can program in a semi-object oriented fashion in C.  You can protect data, expose access functions, etc.  It may not have all of the fanciness of C++, but from what I have seen of other people's C++ code, many people do not use the fanciness anyway.  In other words, people write C code inside a class, where in C you'd write the same code without the class container.</p>

<p>First, read a book on C programming and style, K&amp;R is fine.  Second, I'd recommend checking out <a href="https://www.securecoding.cert.org/confluence/display/seccode/CERT+C+Secure+Coding+Standard" rel="nofollow noreferrer">CERT Programming Standard</a>.  Even though this site is primarily focused on "Secure" coding standards, much of the content here is general code quality standards everyone should follow.  Doing the things mentioned here will improved your quality, eliminate pesky bugs, and as a side effect, make your code more secure.</p>


blocks|key|334817|text|我没有C的专业经验(只在C%2B%2B上)，所以不要把我的建议、技巧和技巧看得太重，因为它们是“面向对象的”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|334818|几乎是对象C？|334819|可以很容易地模拟基本的类似对象的功能：|334820|在头文件中，转发声明你的类型，定义它的类型，并声明“方法”。例如：|334821|/*+MyString.h+*/

#include+<string.h>

/*+Forward+declaration+*/
struct+StructMyString+;

/*+Typedef+of+forward-declaration+(note:+Not+possible+in+C%2B%2B)+*/
typedef+struct+StructMyString+MyString+;

MyString+*+++++++MyString_new()+;
MyString+*+++++++MyString_create(const+char+*+p_pString)+;
void+++++++++++++MyString_delete(MyString+*+p_pThis)+;
size_t+++++++++++MyString_length(const+MyString+*+p_pThis)+;

MyString+*+++++++MyString_copy(MyString+*+p_pThis,+const+MyString+*+p_pSource)+;
MyString+*+++++++MyString_concat(MyString+*+p_pThis,+const+MyString+*+p_pSource)+;

const+char+*+++++MyString_get_c_string(const+MyString+*+p_pThis)+;
MyString+*+++++++MyString_copy_c_string(MyString+*+p_pThis,+const+char+*+p_pSource)+;
MyString+*+++++++MyString_concat_c_string(MyString+*+p_pThis,+const+char+*+p_pSource)+;|code-block|syntax|javascript|334822|你会看到每个函数都有前缀。我选择"struct“的名称，以确保不会与其他代码发生冲突。|334823|您还会看到，我使用了"p_pThis“来保持OO式的想法。|334824|在源文件中，定义您的类型，并定义函数：|334825|/*+MyString.c+*/

#include+"MyString.h"

#include+<string.h>
#include+<stdlib.h>

struct+StructMyString
{
+++char+*++++++m_pString+;
+++size_t++++++m_iSize+;
}+;

MyString+*+MyString_new()
{
+++MyString+*+pMyString+=+malloc(sizeof(MyString))+;

+++pMyString->m_iSize+=+0+;
+++pMyString->m_pString+=+malloc((pMyString->m_iSize+%2B+1)+*+sizeof(char))+;
+++pMyString->m_pString[0]+=+0+;

+++return+pMyString+;
}

/*+etc.+*/|334826|如果您想要“私有”函数(或私有全局变量)，请在C源代码中声明它们是静态的。这样，它们在外面就看不见了：|334827|static+void+doSomethingPrivate()
{
+++/*+etc.+*/
}

static+int+g_iMyPrivateCounter+=+0+;|334828|如果你想继承，那你就大错特错了。如果您认为C中的所有东西都是全局的，包括变量，那么在尝试考虑如何模拟继承之前，您应该获得更多的C经验。|334829|其他。提示|334830|避免多个代码路径。|334831|例如，多个回报是有风险的。例如：|334832|void+doSomething(int+i)
{
+++void+*+p+=+malloc(25)+;

+++if(i+>+0)
+++{
++++++/*+this+will+leak+memory+!+*/
++++++return+;
+++}

+++free(p)+;
}|334833|避免非常量全局变量|334834|这包括“静态”变量(不是静态函数)。|334835|全局非常量变量几乎总是一个糟糕的想法(例如，参见C+API+strtok了解一个糟糕的函数示例)，如果生成多线程安全的代码，处理它们将是一件痛苦的事情。|334836|避免名称冲突|334837|为你的函数和你的定义选择一个“命名空间”。这可能是：|334838|#define+GROOVY_LIB_x_MY_CONST_INT+42

void+GroovyLib_dosomething()+;|334839|注意定义|334840|定义在C中是无法避免的，但它们可能会有副作用！|334841|#define+MAX(a,+b)+(a+>+b)+?+(a)+:+(b)

void+doSomething()
{
+++int+i+=+0,+j+=+1,+k+;
+++k+=+MAX(i,+j)+;+++/*+now,+k+==+1,+i+==+0+and+j+==+1+*/
+++k+=+MAX(i,+j%2B%2B)+;+/*+now,+k+==+2,+i+==+0+and+j+==+3,+NOT+2,+and+NOT+1+!!!+*/
}|334842|初始化你的变量|334843|避免在未初始化变量的情况下声明变量：|334844|int+i+=+42+;+/*+now+i+=+42+*/
int+j+;++++++/*+now+j+can+have+any+value+*/
double+k+;+++/*+now+f+can+have+any+value,+including+invalid+ones+!+*/|334845|未初始化的变量是导致痛苦的bug的原因。|334846|了解所有的C+API|334847|在K&R中描述的C+API函数列表非常小。你将在20分钟内读完整个清单。您必须了解这些函数。|334848|想要一些经验吗？|334849|重写C+API。例如，尝试编写您自己版本的string.h+.h函数，看看它是如何完成的。|334850|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|28|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|29|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|2A|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|2B|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|2C|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|2D|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|2E|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|2F|8|@]|9|@]|A|$]]|$1|S|3|T|5|J|7|2G|8|@]|9|@]|A|$K|L]]|$1|U|3|V|5|6|7|2H|8|@]|9|@]|A|$]]|$1|W|3|X|5|J|7|2I|8|@]|9|@]|A|$K|L]]|$1|Y|3|Z|5|6|7|2J|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|2K|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|2L|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|2M|8|@]|9|@]|A|$]]|$1|16|3|17|5|J|7|2N|8|@]|9|@]|A|$K|L]]|$1|18|3|19|5|6|7|2O|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|6|7|2P|8|@]|9|@]|A|$]]|$1|1C|3|1D|5|6|7|2Q|8|@]|9|@]|A|$]]|$1|1E|3|1F|5|6|7|2R|8|@]|9|@]|A|$]]|$1|1G|3|1H|5|6|7|2S|8|@]|9|@]|A|$]]|$1|1I|3|1J|5|J|7|2T|8|@]|9|@]|A|$K|L]]|$1|1K|3|1L|5|6|7|2U|8|@]|9|@]|A|$]]|$1|1M|3|1N|5|6|7|2V|8|@]|9|@]|A|$]]|$1|1O|3|1P|5|J|7|2W|8|@]|9|@]|A|$K|L]]|$1|1Q|3|1R|5|6|7|2X|8|@]|9|@]|A|$]]|$1|1S|3|1T|5|6|7|2Y|8|@]|9|@]|A|$]]|$1|1U|3|1V|5|J|7|2Z|8|@]|9|@]|A|$K|L]]|$1|1W|3|1X|5|6|7|30|8|@]|9|@]|A|$]]|$1|1Y|3|1Z|5|6|7|31|8|@]|9|@]|A|$]]|$1|20|3|21|5|6|7|32|8|@]|9|@]|A|$]]|$1|22|3|23|5|6|7|33|8|@]|9|@]|A|$]]|$1|24|3|25|5|6|7|34|8|@]|9|@]|A|$]]|$1|26|3|-4|5|6|7|35|8|@]|9|@]|A|$]]]|27|$]]

<p>I have no professionnal experience on C (only on C++), so don't take my advices, tricks and tips too seriously, as they are "object-like-oriented".</p>

<h2>Almost Object C?</h2>

<p>Simulating basic object-like features can be done easily:</p>

<p>In the header, forward declare your type, typedef it, and declare the "methods". For example:</p>

<pre><code>/* MyString.h */

#include &lt;string.h&gt;

/* Forward declaration */
struct StructMyString ;

/* Typedef of forward-declaration (note: Not possible in C++) */
typedef struct StructMyString MyString ;

MyString *       MyString_new() ;
MyString *       MyString_create(const char * p_pString) ;
void             MyString_delete(MyString * p_pThis) ;
size_t           MyString_length(const MyString * p_pThis) ;

MyString *       MyString_copy(MyString * p_pThis, const MyString * p_pSource) ;
MyString *       MyString_concat(MyString * p_pThis, const MyString * p_pSource) ;

const char *     MyString_get_c_string(const MyString * p_pThis) ;
MyString *       MyString_copy_c_string(MyString * p_pThis, const char * p_pSource) ;
MyString *       MyString_concat_c_string(MyString * p_pThis, const char * p_pSource) ;
</code></pre>

<p>You'll see each functions is prefixed. I choose the name of the "struct" to make sure there won't be collision with another code.</p>

<p>You'll see, too, that I used "p_pThis" to keep with the OO-like idea.</p>

<p>In the source file, define your type, and define the functions:</p>

<pre><code>/* MyString.c */

#include "MyString.h"

#include &lt;string.h&gt;
#include &lt;stdlib.h&gt;

struct StructMyString
{
   char *      m_pString ;
   size_t      m_iSize ;
} ;

MyString * MyString_new()
{
   MyString * pMyString = malloc(sizeof(MyString)) ;

   pMyString-&gt;m_iSize = 0 ;
   pMyString-&gt;m_pString = malloc((pMyString-&gt;m_iSize + 1) * sizeof(char)) ;
   pMyString-&gt;m_pString[0] = 0 ;

   return pMyString ;
}

/* etc. */
</code></pre>

<p>If you want "private" functions (or private global variables), declare them static in the C source. This way, they won't be visible outside:</p>

<pre><code>static void doSomethingPrivate()
{
   /* etc. */
}

static int g_iMyPrivateCounter = 0 ;
</code></pre>

<p>If you want inheritance, then you're almost screwed. If you believed everything in C was global, including variable, then you should get more experience in C before even trying to think how inheritance could be simulated.</p>

<h2>Misc. Tips</h2>

<h3>Avoid multiple code-paths.</h3>

<p>For example, multiple returns is risky. For example:</p>

<pre><code>void doSomething(int i)
{
   void * p = malloc(25) ;

   if(i &gt; 0)
   {
      /* this will leak memory ! */
      return ;
   }

   free(p) ;
}
</code></pre>

<h3>Avoid non-const globals</h3>

<p>This include "static" variables (which are not static functions).</p>

<p>Global non-const variables are almost always a bad idea (i.e. see C API strtok for an example of crappy function), and if producing multithread safe code, they are a pain to handle.</p>

<h3>Avoid name collision</h3>

<p>Choose a "namespace" for your functions, and for your defines. This could be:</p>

<pre><code>#define GROOVY_LIB_x_MY_CONST_INT 42

void GroovyLib_dosomething() ;
</code></pre>

<h3>Beware defines</h3>

<p>Defines can't be avoided in C, but they can have side effects!</p>

<pre><code>#define MAX(a, b) (a &gt; b) ? (a) : (b)

void doSomething()
{
   int i = 0, j = 1, k ;
   k = MAX(i, j) ;   /* now, k == 1, i == 0 and j == 1 */
   k = MAX(i, j++) ; /* now, k == 2, i == 0 and j == 3, NOT 2, and NOT 1 !!! */
}
</code></pre>

<h3>Initialize your variables</h3>

<p>Avoid declaring variables without initializing them:</p>

<pre><code>int i = 42 ; /* now i = 42 */
int j ;      /* now j can have any value */
double k ;   /* now f can have any value, including invalid ones ! */
</code></pre>

<p>Uninitialized variables are causes of painful bugs.</p>

<h3>Know all the C API</h3>

<p>The C API function list as described in the K&amp;R is quite small. You'll read the whole list in 20 minutes. You must know those functions.</p>

<h3>Wanna some experience?</h3>

<p>Rewrite the C API. For example, try to write your own version of the string.h functions, to see how it is done.</p>


blocks|key|3097187|text|你可能有兴趣看看我不久前问过的一个similar+question的答案。此外，如果你对C风格的指南感兴趣，你可能想看看this+page，因为它是C(和C%2B%2B)风格指南的存储库。如果你有心情来一次good+look+，请看看NASA+C+Style+Guide。尤其是，看看大量的评论...你就知道我说的是哪一个了。请不要这样写评论。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3097188|我个人推荐带一些修改的Indian+Hill+C+Style+Guide。此外，如果您在用C语言设计大型程序时遇到困难，您可能需要购买C+Interfaces+and+Implementations这本书。|3097189|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/415452/object-orientation-in-c|1|http://www.maultech.com/chrislott/resources/cstyle/|2|http://web.archive.org/web/20190125125043/http://homepages.inf.ed.ac.uk/dts/pm/Papers/nasa-c-style.pdf|3|http://www.maultech.com/chrislott/resources/cstyle/indhill-cstyle.pdf|4|http://www.cs.princeton.edu/software/cii/^0|2R|A|H|G|0|1O|9|1|35|I|2|0|B|P|3|1V|W|4|0^^$0|@$1|2|3|4|5|6|7|X|8|@$9|Y|A|Z|B|C]]|D|@$9|10|A|11|1|12]|$9|13|A|14|1|15]|$9|16|A|17|1|18]]|E|$]]|$1|F|3|G|5|6|7|19|8|@]|D|@$9|1A|A|1B|1|1C]|$9|1D|A|1E|1|1F]]|E|$]]|$1|H|3|-4|5|6|7|1G|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]|P|$5|K|L|M|E|$N|Q]]|R|$5|K|L|M|E|$N|S]]|T|$5|K|L|M|E|$N|U]]|V|$5|K|L|M|E|$N|W]]]]

<p>You may be interested in checking out the answers to a <a href="https://stackoverflow.com/questions/415452/object-orientation-in-c" title="Object-Orientation in C">similar question</a> I asked not too long ago. Moreover, if you're interested in C style guides, you may want to take a look at <a href="http://www.maultech.com/chrislott/resources/cstyle/" rel="noreferrer" title="C and C++ Style Guides">this page</a> since it is a repository for C (and C++) style guides. If you're in the mood for a <strong>good laugh</strong>, please take a  look at the <a href="http://web.archive.org/web/20190125125043/http://homepages.inf.ed.ac.uk/dts/pm/Papers/nasa-c-style.pdf" rel="noreferrer" title="NASA C Style Guide">NASA C Style Guide</a>. In particular, take a look at the <em>massive</em> comment... you'll know which one I'm talking about. Don't write comments like this please.</p>

<p>I personally recommend the <a href="http://www.maultech.com/chrislott/resources/cstyle/indhill-cstyle.pdf" rel="noreferrer" title="Indian Hill C Style Guide">Indian Hill C Style Guide</a> with some modifications. Furthermore, you may want to purchase the book <a href="http://www.cs.princeton.edu/software/cii/" rel="noreferrer" title="C Interfaces and Implementations">C Interfaces and Implementations</a> if you're having trouble designing large-scale programs in C.</p>


blocks|key|333709|text|你可能想好好看看Linux内核的源代码.....顺便说一句，它不是最容易开始的代码，但由于你来自编程背景，它可能会有所帮助……作为一名面向对象的程序员，您可能会特别发现C中的错误处理是一项艰巨的任务。这可能会有帮助->+http://www.freetype.org/david/reliable-c.html|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|333710|entityMap|0|LINK|mutability|MUTABLE|url|https://web.archive.org/web/20121102161639/https://www.freetype.org/david/reliable-c.html^0|32|19|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

<p>You may want to have a good look at the source of The Linux Kernel..... BTW it is not the easiest piece of code to start with but since you are from a programming background, it may help... As an object-oriented programmer, you might particularly find error-handling in C an uphill task. May be this helps---> <a href="https://web.archive.org/web/20121102161639/https://www.freetype.org/david/reliable-c.html" rel="nofollow noreferrer">http://www.freetype.org/david/reliable-c.html</a></p>


blocks|key|334887|text|如果您对关键环境标准感兴趣，那么MISRA+C可能会对您感兴趣。我发现它很有帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|334888|你可以得到MISRA+C2004+here。|offset|length|334889|更新的MISRA+C+2012+here的简短概述。|334890|entityMap|0|LINK|mutability|MUTABLE|url|http://caxapa.ru/thumbs/468328/misra-c-2004.pdf|1|http://my.ldrasoftware.co.uk/repository//miscellaneous/Misra-c_2012_compliance.pdf^0|0|H|4|0|0|G|4|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|Q]]]]

<p>If you are interested in critical environment standards, then MISRA C could be of interest to you. I found it helpful.</p>

<p>You can get MISRA C 2004 <a href="http://caxapa.ru/thumbs/468328/misra-c-2004.pdf" rel="nofollow noreferrer">here</a>.</p>

<p>Short overview of the updated MISRA C 2012 <a href="http://my.ldrasoftware.co.uk/repository//miscellaneous/Misra-c_2012_compliance.pdf" rel="nofollow noreferrer">here</a>.</p>


<p>I come from a java background (from my CS classes) and a semester of C++.  I am just finishing up a OpenCV project for my Co-Op that's in pure C, so I'm a bit late in asking this question.</p>

<p><strong>What are the design processes and coding standards for pure C?</strong>   </p>

<p>I'm familiar with object oriented programming, design and best practices.  I'm just a bit at a loss at a non-object oriented language like C.  Every single variable and function appears to be global.  It makes it feel like a real mess to me.</p>


Coding Standards for pure C (not C++)

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我来自java背景(来自我的CS课程)和一个学期的C++。我刚刚为我的Co-Op完成了一个纯C语言的OpenCV项目，所以我问这个问题有点晚了。纯C语言的设计过程和编码标准是什么？我熟悉面向对象编程、设计和最佳实践。我只是对像C这样的非面向对象语言有点迷惑，每个变量和函数似乎都是全局的。这让我觉得它真的一团糟。

问纯C语言的编码标准(不是C++)
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问纯C语言的编码标准(不是C++)EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问纯C语言的编码标准(不是C++)
EN