They have also provided you with the following.
.infoz files
that correspond to the "adventure" bookz they provided earlier.
You must uncompress it (using gzip) and extract the
individual files (using tar) before using it, but you
must not change any of the individual file names or the contents of
the files.
bookz_lib
library).
b,
both the zplayer process and the bookz_player process must have been
terminated.
.infoz file associated with the
current .bookz file must be read at most once (per session).
.zip file you submit must be named pa4.zip.
In addition to the source code and makefile, the .zip
file must contain four screenshots of the output from
ps. Specifically, it must contain: one
(named before.png) that shows the current processes
before you run zplayer, one (named ready.png) that shows
the current processes when zplayer is in the Ready state, one
(named playing.png) that shows the current processes
when zplayer is in the Playing state, and one
(named after.png) that shows the current processes
after zplayer has terminated.
You must not submit any data files.
Since you must use the bookz_player program and not the bookz_lib,
the zplayer must exec the bookz_player.
Note that you will not be able to do this easily on stu
(since stu does not support windowing you must login
twice to have two terminals active at the same time). Hence, you will want
to work on your computer or a lab computer.
char values that you are using. As you know from the
previous assignment, there is a correspondence between the two. You
were told which char values to use in some cases and
were allowed to choose the char values in other cases.
For this assignment, there is only one new correspondence --
the get_info event corresponds to the char literal
'?'.
Your code should treat the user-generated events (like the old load and go, and the new get_info) similarly. If it isn't then you are probably doing something wrong. In particular, you should not need to prompt for any of these events/key-presses in the individual states, that should all be handled in the zplayer.
.infoz file corresponding
to the .bookz file. (There are several variants of this --
while in the Ready state for the first time, while in the Ready state for
the n
th time, and while in the Playing state.)
When testing, it will probably be convenient to create files that contain the characters you would normally enter using the keyboard and then redirect standard input (so that you don't have to keep typing the same think over and over).
Copyright 2017