Back to Operating Systems Home Page
Next: File descriptors across fork(2)/exec(2)
Up: 1997 term messages
Previous: About initializing semaphores
Whoa, one more than the seven biblical ones...Well, not exactly deadly, but
most common in your assignments. BTW - I think this one (#2) went
much better overall then the first one, congrats. However, here are
some points to watch in the future
Introducing your charming T.A.'s findings, [with my comments in brackets]
---------- Forwarded message ----------
Date: Mon, 10 Mar 1997 08:48:36 -0500 (EST)
From: Annie Kwong <annekwon@ee.mcgill.ca>
To: Francesco Callari <franco@cim.mcgill.ca>
Subject: assignment2
Hi,
after going through the assignment 2, I found out that the errors
that people generally made are:
1. Didn't allow user mistake in input to be recovered.
[Program not robust]
2. Didn't check for exception when using system call.
[Really really bad. Never assume the system is nice to you,
because it isn't -- beat it into submission.]
3. Mis-understand specification.
[SUBLIMINAL MESSAGE - Read the text Ask Read the text Ask Read the
text Ask]
4. Didn't do the doc.
5. Didn't comment their code.
[Ehi, the TAs and I are not followers of JoJo: we can't read
your inner thoughts unless you write them, sorry.]
6. Use unmeaningful variable name ( very hard and time consuming to
read).
[Oh, so I can't call my nice variables "qkhjAyhF" and "qkBnslP"?]
7. Didn't understand the system call.
[SUBLIMINAL MESSAGE - man man man man man man man man man]
8. Didn't do wait()
[I see them...they are here...arghhhh..help..the ZOMBIES!]
---------- End forwarded message ----------
\
Franco Callari