Good point. I think what we really need to see is the code that is being compiled not the code in the PDF.Me neither, I can't see any mistake in the posted code .. I think Also and as mentioned in the posted PDF file it would be necessary to rewrite the code as it must be will commented and easily understandable.
The problem in this case is compiling and running this example does not gain anything. It will appear to work just fine. One could argue you could then put it through valgrind or what not, but I wouldn't expect a student to know about tools like that. I have to agree with the OP that putting it in a compilable form is not necessary. In my opinion, for this particular example, anyone that can't see the problem and requires it to be compiled is probably not qualified to answer the question.When you do programming training, the least you can do when you work a problem is to type it, compile it and then check for compilation errors. Anything less isn't really considered effort.
|Thread starter||Similar threads||Forum||Replies||Date|
|USB memory sticks. Too good to be true?||General Electronics Chat||15|
|RAM memory works at 1066MHz instead of 1333MHz||General Electronics Chat||0|
|Memory leak somewhere in Raspberry Pi 3||Microcontrollers||7|
|R||Intel Kernel Memory Leak||General Electronics Chat||57|
|B||How to find memory leak and how to resolve it on embedded systems||Microcontrollers||7|
by Cabe Atwell
by Robert Keim