 |
.. (לתיקייה המכילה) | |
How specific should be suggestions for class simplification? | |
|
The suggestions should be like: - instead of code fragment X the code fragment Y can be written. - an auxiliary function F can be defined (function definition) and so on Numer of reduced code lines should be estimated for each suggestion. |
Do we need to simplify the whole InstConstraintVisitor class or just the method visitGETFIELD ? | |
|
For the class simplification you are not required to change the class code. Just to describe suggestions for improovement. Also you are not required to implement all simplification techniques, the main goal is to make the class shorter. For the method visitGETFIELD you need to write full simplification in the java file. |
Do we need to write in solution the visitGETFIELD simplification process? | |
| Yes. Main steps at least. |
Do we need to fix every warning that can be fixed? | |
| You need to fix warnings that are relevant for simplification. |
What should be written in solution about warnings? | |
|
List of warnings that are relevant for simplification: - fixed warnings with solution - warnings that can't be fixed with explanation (if you find such warnings) |