gratuitous differences in style from one function to another. If your
code is too ugly, it will cost you points.
+Please limit C source file lines to at most 79 characters long.
+
Pintos comments sometimes refer to external standards or
specifications by writing a name inside square brackets, like this:
@code{[IA32-v3]}. These names refer to the reference names used in
If you remove existing Pintos code, please delete it from your source
file entirely. Don't just put it into a comment or a conditional
compilation directive, because that makes the resulting code hard to
-read. If you're worried about
+read. We're only going to do a compile in the directory for the current
+project, so you don't need to make sure that the previous projects also
+compile.
@node Conditional Compilation
@section Conditional Compilation
There are a few exceptions:
@itemize @bullet
-@item
-Problem 1-2, @func{thread_join}. Some other code expects
-@code{THREAD_JOIN_IMPLEMENTED} to be defined once you've implemented
-this function.
-
@item
Problem 1-4, the advanced scheduler. We must be able to turn this on
and off with a compile-time directive. You must use the macro name we
@func{strlcpy}.
@item strcat
-Same issue as @func{strcpy}, but substitute @func{strlcat}.
+Same issue as @func{strcpy}. Use @func{strlcat} instead.
Again, refer to comments in its source code in @code{lib/string.c} for
documentation.