标签：24 重构 level replace refactoring too routine class

Reasons to refactor:

1. code is duplicated;
2. A routine is too long; A routine has a poor name;
3. A loop is too long or too deeply nested;
4. A class has poor cohesion; A class interface does not provide a consistent level of abstraction; One class is overly intimate with another;
5. A parameter list has too many parameters;
6. Data members are public;
7. Global variables are used;

Refactorings:

1. Data-level refactoring;
2. statement-level refactoring;
3. routine-level refactoring;
4. class implementation refactoring;
5. class interface refactoring;
6. system-level refactoring.

TIPS:

• replace a magic number with a named constant;
• rename a variable with a clearer or more informative name;
• replace an expression with a routine;
• convert a multi-use variable to multiple single-use variables;
• replace a traditional record with a data class;
• change value objects to reference objects;
• create a definitive reference source for data you can't control;
• provide a factory method rather than a simple constructor.

标签：24,重构,level,replace,refactoring,too,routine,class
来源： https://blog.csdn.net/qq_40732962/article/details/112061983

本站声明： 1. iCode9 技术分享网（下文简称本站）提供的所有内容，仅供技术学习、探讨和分享；
2. 关于本站的所有留言、评论、转载及引用，纯属内容发起人的个人观点，与本站观点和立场无关；
3. 关于本站的所有言论和文字，纯属内容发起人的个人观点，与本站观点和立场无关；
4. 本站文章均是网友提供，不完全保证技术分享内容的完整性、准确性、时效性、风险性和版权归属；如您发现该文章侵犯了您的权益，可联系我们第一时间进行删除；
5. 本站为非盈利性的个人网站，所有内容不会用来进行牟利，也不会利用任何形式的广告来间接获益，纯粹是为了广大技术爱好者提供技术内容和技术思想的分享性交流网站。