0

I probably almost got my pset6 working. When I run the check50 on it, it says:

:( handles possessives properly    \ expected output, not standard
error of "/opt/sandbox50/bin/run.sh: line 31: 184..."

:( handles substrings properly    \ expected output, not standard
error of "/opt/sandbox50/bin/run.sh: line 31: 182..."

Here is the link to check50's output!

I have no idea what the error is here. The program passes other tests.

Can you tell me where my program fails?

I struggle to write the word possessives with the correct amount of s'. It's like Alanis' last name.

Improve this question

1 Answer 1

Reset to default
0

When the word "Agetribe" is in the dictionary, but the word "Agetribe's" or "Agetribes'" are not, your program should consider "Agetribe's" and "Agetribes'" as a misspelled words and vice-versa unless they're all in the dictionary.

This has to do with inserting apostrophes (i.e., ') and marking the end of words.

When the word "Agetribe" is in the dictionary, but part of it (e.g., "Age", "get", ...) is not, your program should consider that part as a misspelled word unless it's already in the dictionary.

This also has to do with marking the end of words.

Improve this answer
8
  • I understand what you are saying but why do I get then error instead of wrong output? /opt/sandbox50/bin/run.sh: line 31: 21084 Segmentation fault stdbuf --error=0 --output=0 "$@" The error is somewhere in checkers code which my code triggers? Also when I compare my output with staff solution in Austin Powers, Witch and Dracula the output is exactly the same.
    – Agetribe
    Commented Jul 18, 2014 at 2:48
  • 1
    @Agetribe you seem to be getting a segmentation fault. The problem seems to be online 31. If you'd like me to help you identify the bug in your code, you may send me the source code file at [email protected]!
    – kzidane
    Commented Jul 18, 2014 at 11:04
  • Thank you very much for your offer, no need for you to look at the code, it is what it is. I changed my code so that there is nothing on the line 31. Still the error is the same. I thought that the error is on the line of the checker program. As I have no idea what is wrong I decided to move forward and accepted the 0.67 score.
    – Agetribe
    Commented Jul 19, 2014 at 14:16
  • @Agetribe FYI, you can still resubmit your solution to the pset after fixing the bugs to get the full grade if you wish!
    – kzidane
    Commented Jul 19, 2014 at 15:00
  • 1
    @Agetribe well, sometimes it's difficult to tell where exactly the problem is without seeing some code as it's difficult for a doctor to diagnose a disease without seeing the patient! You may update your question with some pseudocode!
    – kzidane
    Commented Jul 19, 2014 at 21:36

You must log in to answer this question.

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