0

When I write check50 2014/x/pset2/caesar caesar.c in the command line or the terminal this is what happens:

:) caesar.c exists
:) caesar.c compiles
:) encrypts "a" as "b" using 1 as key
:) encrypts "barfoo" as "yxocll" using 23 as key
:) encrypts "BARFOO" as "EDUIRR" using 3 as key
:) encrypts "BaRFoo" as "FeVJss" using 4 as key
:) encrypts "barfoo" as "onesbb" using 65 as key
:) encrypts "world, say hello!" as "iadxp, emk tqxxa!" using 12 as key
:( handles lack of argv[1]
 \ expected output, not an exit code of 1

Why is the last line :(?

2
  • thank you sir!! Aug 4 '14 at 19:46
  • 1
    You're welcome. Here on StackExchange, rather than saying 'thank you', you can upvote the answer and/or accept it. That way, others know the question has been solved.
    – curiouskiwi
    Aug 4 '14 at 19:57
5

The spec requires you to print a message to the user before returning 1. Looks like you aren't.

3
  • thanks, but what message should i print Aug 4 '14 at 19:38
  • 1
    Anything that makes sense to help the user. Check50 only checks that you printed something.
    – curiouskiwi
    Aug 4 '14 at 19:39
  • thank you sir!! Aug 4 '14 at 19:48

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