In general, good programming style says you put in comments that are going to be valuable in helping you as a reader understand what's going on inside of the code.
通常来说,优秀的编码风格意味着,你要放进去的注释,在帮助代码阅读者,理解代码内部,是怎么工作的。
What we recommend is you use those notes to take your own annotations to help you understand what's going on, but we're not going to provide class notes.
我们的建议是,你用那些笔记去做你自己的注释,从而帮助你理解在学什么,然而我们不会提供课堂笔记。
Because as you'll soon find, when you're writing programs 0 that aren't just four lines long but are 40 or 400 which very quickly becomes easy, you'll find that even you the next morning have no idea what this code does for whatever reason, and just having some English comments is a huge boon to comprehension for yourself and others.
你们自己写程序时就会发现,用40行甚至400行代码来代替繁杂拥挤的4行代码0,将会让事情简化许多,你会发现,即使由于某些原因,你不知道如何写代码,先写些注释,于人于己,都是好事,易于理解嘛。
There is no reference, in any of the tablets-- I don't know how much we can make of that because the tablets limit themselves to such limited kinds of things that maybe it doesn't prove anything, but in this case, I think it does.
在所有陶土碎片的文字中都没有注释,我不知道我们能够理解多少,况且陶土碎片可供记录的空间有限,也许它们不能证明任何东西,但在这里,我想至少可以证明一点
So let's take a look then at somewhere where this is actually a useful thing to know so this is compare1.c. So, in compare1.c I've stripped out the comments in my version but in your version you do have comments for reference and it's actually pretty self-explanatory if you just read through the code.
那么再然我们看一看,一些有用的东西,这是compare1。c,所以在compare1。c中,在我的版本中,我吧注释去掉了,但是在你们的版本中是有注释的,这是相当容易理解的,如果你通读这段代码。
应用推荐