Contributions are very welcomed and needed, if you want to contribute please open a Pull Request following the directory structure:
An effort is made to have the code be concise and readable.
semester/L#/submitter's name/
|
Note
|
I won’t include the PDFs with the problem statement because I don’t have permission to share them publicly on the internet. If you have a PUCP email, you can either access Prof. Cueva’s Google Drive or AAII's Google Drive , you can find the some PDFs there. |
Many times, compilation or runtime error messages are not helpful or borderline cryptic. Debugging tools help a lot. But narrowing down what component most likely failed is of great help. Develop each "module" separately, compile and debug frequently. Make sure each "module" works fine before moving to the next one.
You should definitly make effective use the debugging tools from the IDE (breakpoints, keybindings, call stack, watches, expressions). Otherwise you are just waisting your time. Most IDE either use GDB or LLDB, and they share most of the basic concepts. You can learn the basics fast and start practicing.
Prof. Guanira states it clearly in "Guia de Creacion Ejecucion y Depuracion.pdf":
Using
stream manipulators and
stream format flags can be cumbersome, but the course requires them since
using printf is not allowed. So maybe macros can be helpful here.
See tips/formatting.adoc for an example implementation and usage.