Today's task is more advanced than the previous exercises, and more realistic; it is still simplified compared to a real situation, but this one doesn't just consist in writing some short functions.
Before doing this you need to be good with Scheme, and with Unix.
If you have not finished the second TP then I suggest to complete it before starting this. I prefer not to speak about advanced Scheme features until I'm sure that most people have understood the content of the second TP.
You can find some practical suggestions at the bottom of the first TP page.
I've seen that many people didn't subscribe to the mailing list yet,
so chances are that you didn't either;
A student noticed that the page may ask you to accept certificates. Don't worry, the server is at LIPN, Université Paris 13; it's perfectly safe.
guile-game is Guile extended with some functionality added by me
by calling the SDL and SDL_ttf libraries in order to support graphics,
keyboard and mouse events.
You will also use (possibly a newer version of) guile-game for the final project, which is not specified yet.
As usual if you are at the Institut Galilée labs, you have to execute the red line above on each terminal before you start.
Enter the directory within your home where you want to work with guile-game.
Download, uncompress, configure and compile guile-game:
unset http_proxy wget www-lipn.univ-paris13.fr/~saiu/teaching/DLL-2010/big-project/guile-game/guile-game-0.0.5.tar.gz tar xfv guile-game-0.0.5.tar.gz cd guile-game-0.0.5 ./configure makeYou shouldn't see any error message; if everything works you will see the executable files guile-game (it's Guile extended with graphic primitives and event support), server, client and monitor.
There are several test programs, including some relatively complex ones such as last year's big project demo:
./guile-game scm/demos/line-demo.scm ./guile-game scm/big-project-demo-2009/big-project-demo-standalone.scmAnd of course there is the Pong application, which is most important for you today. You can run it with two players by entering all on the same line:
./server ./client ./client ./monitorDon't be afraid of reading the source code when it's needed, or when you're simply curious.
Read about association lists in the Guile manual. Learn the predefined functions for working on association lists; you will need them for the next task.
The three files server, client and monitor are proprietary (for didactic reasons only; I'm gonna publish the complete sources at the end of the course); you have already compiled them from C files, but those C files are not the source code as defined, for example, by the GNU GPL; look at the files src/*proprietary.[ch] . Really: open a couple of them with your text editor and have a look.
client (and also monitor, which is another sort of client) communicates via its standard input
and standard output: it receives information about the current state
in its standard input, decides what move to perform, and emits the move to perform on its
Each message, both input and output, is exactly one (not zero or more than one) Scheme
Of course pong doesn't require much intelligence to play: the problem
is communicating with the right format.
Realistic servers and clients would run across the network, on sockets. The clients of this
application instead use their standard input and standard output, so that you can reverse-engineer
protocols without using network sniffers or more complex software.
The server communicates with clients via pipes, but this isn't interesting for you if you're not developing the server
Read the README file to understand how to run the proprietary Pong
application. Your task is implementing a program similar to
client, which can interact with the proprietary server, in Scheme.
You can observe the behavior of the proprietary version, but you
can't directly access the source.
After you have understood the protocol, the implementation will be easy: my solution in Scheme is less than 70 lines.
Call me if you succeed in implementing a program similar to client.
./server ./monitor 'solution/with-log ./client' ./clientNotice the quotes around solution/with-log ./client: the server must see it as a single option, even if on its own it's a command line (but this is not the only solution: your script may also call the proprietary client internally, and take no options).
Optional: understand the C files src/*proprietary.[ch], and tell me. How was the proprietary application implemented? Tell me.
Optional: can you obtain part of the source code of client in some way? Tell me if you succeed. Optional: about trying to recover part of the source code as just requested: is it legal? Why?
The proprietary client isn't a great player: you can do better and beat it most of the times.
Call me if you succeed in this.
Back to my home page...