In each review session I will give a brief explanation of how the final exam works and what's covered. I will then answer questions about the material from students. The session ends when students run out of questions, or after 90 minutes (whichever comes first).
Links to the review sessions can be found in the Topic Outline, in the Exam Period part of the table.
The difference has an effect on where the middle of the list is. For one version the middle might be 3, while for the other it's 4. That can make a big difference on how fast the value is found (for example, if it's at position 3 or 4).
We're running 100 searches, so the differences should average out -- but they may be off by a little bit. In one solution I was sent the numbers are off-by-one on a few lines of the tables.
I have provided alternate values for some lines in the sample output. You'll see something like
I made some mistakes when setting up the automatic grading for some questions, so I went thru and revised the grades. You might want to check your grade again.
I have also revised the feedback so that it now (I HOPE!) shows you the score you got on each question. (Once again, Brightspace won't let me see what you guys see, so I have to trust it to do what I said. But I don't trust it, because it does lie to me quite a lot.)
You should have created a constant for each of the number of hours in a week (40), the number of weeks in a year (52), the minimum hourly wage (11.55) and the minimum annual salary (1.00). You should then have used those constants in all code that required those numbers. It's only in using those constants in code that we get the advantage of being able to revise any of those values quickly and easily (that is, with less chance of introducing a BUG into our programs).
removeAll
the way it's supposed to be done.
Sorry!
I have made a modification to the code in A04.java
that will test whether you did removeAll
the way I told you to do it,
or the way it's actually supposed to be done.
It then runs the last test
using the appropriate return value
for which way you did it.
No one will be penalized for doing it the way I said. But anyone who figures out the correct way to do it will get bonus points.
So long as you do everything else correctly, you won't see a FAIL message either way.
Note: the changes do not modify the behaviour of the program. They merely resolve some warnings that some compilers and IDEs might have given you.
I have revised the sample output accordingly. Sorry about that!
Welcome to the CSCI 2341 web site for Winter 2024.
Use the navigation bar to the left to find course information, reference material, assignments and grades.
This page (the first you will see when you come to the web site) contains announcements regarding class and assignments that come up between classes. You should check this page if you notice a mistake in the assignment or are having particular trouble with an assignment. You should check occasionally anyway, and look in on it before you submit your assignments.
If you notice a mistake in an assignment (whether the description is inconsistent, or a link is broken, or the sample program does not do what the description says it must) you should e-mail Mark Young right away. The first person to point out a "needs to be fixed" problems will receive up to a 5 percent bonus on that assignment.
Changes to assignments will be posted here, but will also appear on the assignment page in red text.