 |
.. (לתיקייה המכילה) | |
last modified: 10.12
- 29.11: Added 1.
- 5.12: Added 2.
- 6.12: Added 3, 4, 5.
- 10.12: Clarification of 5.
- 29.11: Added 1.
- 5.12: Added 2.
- 6.12: Added 3, 4, 5.
- 10.12: Clarification of 5.
1. Is N a constant for complexity purposes? | |
| N is not a constant. |
2. In the declaration of IsThreatening there is a parameter named "threats" but in the description in the document its name is "moves" instead, which one should be used? | |
| "threats" is the intended name, as it is in library1.h. |
3. What code conventions should we follow? Will points be reduced for ugly, unreadable, nasty, yet efficient, code? | |
|
Points won't be reduced for ugly code, but the code must be readable and coherent with comments to clarify complex/important code and use meaningful variable/function/class/structure names. This is mainly for your benefit. All in all, writing "ugly but efficient" code won't help you at all, and will mainly only increase the time it will take you to debug/fix your code. For more ideas about how to write your code, see the programming tips folder under FAQ for poor programming practices and ways to avoid them. |
4. The declaration of GetAllPieces in the document have the parameter "pieces" of type "PieceOnBoard*" instead of "PieceOnBoard**" as in library1.h, what should be the type? | |
| The type should be like in library1.h, PieceOnBoard**. |
5. Can we use STL just for ... ? | |
| No. You can use STL to debug your program, but the code you submit should not include any code but your own. |