I'm going over lab 4 right now (probably the last one for a while) and have a few suggestions to restructure it.
Remove the inlab4.cpp requirement. There's nothing we can really grade for that part other than "did they write it?". The real benefit is from using the debugger on that file. If removing it as a submittable requirement makes people skip over it, well then shucks, that's on them and they still need to complete the doc somehow.
Move the floating point conversion portion back to the inlab, so that the pre-lab becomes code-submission only and the in-lab becomes worksheet-submission only. Heck, maybe even radix conversion as well from the post-lab. Then we don't need to repeat ourselves thrice about PDFs :). Also, this makes positioning the Hints section a whole lot easier!
I don't know...overall, Lab 4 feels like one of the labs with the least amount of cohesion, even after these proposed changes. It's just a bunch of functions and worksheets all over the place with minimal or no relation to each other. It would be nice to come up with a reworked lab that ties everything together.
I'm going over lab 4 right now (probably the last one for a while) and have a few suggestions to restructure it.
inlab4.cpprequirement. There's nothing we can really grade for that part other than "did they write it?". The real benefit is from using the debugger on that file. If removing it as a submittable requirement makes people skip over it, well then shucks, that's on them and they still need to complete the doc somehow.I don't know...overall, Lab 4 feels like one of the labs with the least amount of cohesion, even after these proposed changes. It's just a bunch of functions and worksheets all over the place with minimal or no relation to each other. It would be nice to come up with a reworked lab that ties everything together.