改良程序的技巧（Techniques for improving procedures）.docVIP

下载本文档

0
0
约8.69千字
约 10页
2017-09-28 发布于河南
举报
版权申诉

改良程序的技巧（Techniques for improving procedures）.doc

1、原创力文档（book118）网站文档一经付费（服务费），不意味着购买了该文档的版权，仅供个人/单位学习、研究之用，不得用于商业用途，未经授权，严禁复制、发行、汇编、翻译或者网络传播等，侵权必究。。
2、本站所有内容均由合作方或网友上传，本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺！文档内容仅供研究参考，付费前请自行鉴别。如您付费，意味着您自己接受本站规则且自行承担风险，本站不退款、不进行额外附加服务；查看《如何避免下载的几个坑》。如果您已付费下载过本站文档，您可以点击这里二次下载。
3、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等，请点击“版权申诉”（推荐），也可以打举报电话：400-050-0827(电话支持时间：9:00-18:30)。
4、该文档为VIP文档，如果想要下载，成为VIP会员后，下载免费。
5、成为VIP后，下载本文档将扣除1次下载权益。下载后，不支持退款、换文档。如有疑问请联系我们。
6、成为VIP后，您将拥有八大权益，权益包括：VIP文档下载权益、阅读免打扰、文档格式转换、高级专利检索、专属身份标志、高级客服、多端互通、版权登记。
7、VIP文档为合作方或网友上传，每下载1次，网站将根据用户上传文档的质量评分、类型等，对文档贡献者给予高额补贴、流量扶持。如果你也想贡献VIP文档。上传文档

改良程序的技巧（Techniques for improving procedures）

改良程序的技巧（Techniques for improving procedures） There are many reasons why we should write clear and readable programs. The most important thing is that you write only once, but you will read it countless times later. When you look back at your code for second days, youre going to start reading it. When you show the code to someone else, he has to read your code. So, spend more time in writing, and you will There are many reasons why we should write clear and readable programs. The most important thing is that you write only once, but you will read it countless times later. When you look back at your code for second days, youre going to start reading it. When you show the code to someone else, he has to read your code. So, spend more time writing, and youll save a lot of time while reading it. Lets look at some basic programming techniques: 1. try to keep the method short 2. never ever use the same variable for several different purposes 3. use self described variable names and method names 4. define variables as close as possible to where they are used 5. deny mysterious numbers 6. be friendly to your language 7. dont go against the routine 8. guard against premature optimization 9. actively refactor the tested program 10. dont indulge in skills 11. learn new knowledge through examples Now, lets expand each of these dots in detail. 1. try to keep the method short Although many people follow this rule, it is still very important. The method you write can always be placed in one screen. If you need to scroll the screen, it distracts you, and you cant see the whole context. The best length is 5-20 lines, which depends on your case. Of course, getters/setters is usually a line of code, but rather than a real method, they are just access tools. 2. never ever use the same variable for several different purposes A variable should always serve only one purpose. By making variable constant (C++ const, Java final), the compiler can optimize the compiler, and make your code stri