Hi,

Thanks for pointing that out! You are correct - the method needs a return type, which should be void in this case. I'll add that.

It might be worth pointing out that documentation testing, which was mentioned in lectures, is a good way of avoiding problems like these, and it is used for the code in some labs (including lab 4, although not for the code fragment you pointed out).

Several of the code samples in the lab worksheet get automatically extracted and checked to make sure they compile – the source I use for the lab sheet contains Python code like the following to run tests:

from subprocess import run
try:
  run(["javac", "CollapseClass.java"], check=True)
except Exception as ex:
  print("\n\n***JAVAC FAILED: ", ex, "***", sep="");

However, the test code does add extra complexity, and developers need to remember to add it for all code snippets. In this case, setMinutes is a small fragment that I added to the solutions this year, and it doesn't include surrounding test code.

Cheers,

Arran

Another minor update to a labsheet I thought I'll mention, lab 4 at the bottom it has an example function:

" public setMinutes(int minutes) { this.minutes = minutes; } "

I believe the method signature should be: "void setMinutes(int minutes)"