Inconsistency in output specifications and sample executables!

[Thom Bohdanowicz]

I've discovered a small inconsistency between the Program Output
Specifications document we were given, and the output generated by the
most recent sample executables:

the program output specifications state that the first user prompt should be

"
Would you like to play the regular(r) or alternate(a) version of the game?
"

noting the ">" at the beginning of the user input line.

The both sample executables, however, do the following:

"
Would you like to play the regular(r) or alternate(a) version of the game?

"

where this time there is a lack of ">" at the start of the user input line.

Should our code be made to match the output specification file (i.e.
print the ">", which will cause our program's output to not precisely
match the sample executable output via diff), or should we follow the
sample executable's lead and omit the ">" so that we match the sample
executable exactly?

Thanks,

-Thom

[Terry Anderson]

You should always be sure to exactly match the sample executable, as this
is what is used to mark the correctness portion of the project.
--
Terry Anderson
CS 246 Instructor

Post by Thom Bohdanowicz
I've discovered a small inconsistency between the Program Output
Specifications document we were given, and the output generated by the most
the program output specifications state that the first user prompt should be
"
Would you like to play the regular(r) or alternate(a) version of the game?
"
noting the ">" at the beginning of the user input line.
"
Would you like to play the regular(r) or alternate(a) version of the game?
"
where this time there is a lack of ">" at the start of the user input line.
Should our code be made to match the output specification file (i.e. print
the ">", which will cause our program's output to not precisely match the
sample executable output via diff), or should we follow the sample
executable's lead and omit the ">" so that we match the sample executable
exactly?
Thanks,
-Thom