0

I would like to test my whodunit.c that I wrote for as described here with check50.

In the last psets there was always a code line for the proper call of check50 in the pset-description, like on here referring e.g. to

check50 2014.fall.pset2.initials initials.c

Unfortunately this is not the case in . I thought that this couldn't be too difficult so I used Google and found this

check50 2014/x/pset4/whodunit whodunit.c

(using / instead of .) and various other forms how people seem to work with check50.

For in I have tried:

check50 2014/x/pset4/whodunit whodunit.c
check50 2014/x/pset4/bmp/whodunit whodunit.c
check50 2014.x.pset4.whodunit whodunit.c
check50 2014.x.pset4.bmp.whodunit whodunit.c
check50 2014/fall/pset4/whodunit whodunit.c
check50 2014/fall/pset4/bmp/whodunit whodunit.c
check50 2014.fall.pset4.whodunit whodunit.c
check50 2014.fall.pset4.bmp.whodunit whodunit.c

and unfortunately I got "Checking.. invalid ID" every time.

Do you have any idea what I am doing wrong?

Cheers

Cornelius

1 Answer 1

1

Per the spec:

Rest assured that more than one solution is possible. So long as Mr. Boddy’s drawing is identifiable (by you), no matter its legibility, Mr. Boddy will rest in peace.

Because whodunit can be implemented in several ways, you won’t be able to check your implementation’s correctness with check50. And, lest it spoil your fun, the staff’s solution to whodunit is not available.

So there is not a check50 for this pset.


If this answers your question please accept it by clicking the gray check-mark to the left, so that it becomes green. You can also vote it up by pressing the up arrow above the check-mark. And don't forget to keep coding!

1
  • thanks for this. my mistake.
    – Cornelius
    Commented Oct 6, 2015 at 15:09

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .