different style won't cause actual problems, but it's ugly to see
gratuitous differences in style from one function to another.
+Pintos comments sometimes refer to outside standards or
+specifications by writing a name inside square brackets, like this:
+@code{[IA32-v3]}. These names refer to the reference names used in
+this documentation (@pxref{References}).
+
@node Conditional Compilation
@section Conditional Compilation
There are a few exceptions:
@itemize @bullet
+@item
+Problem 1-2, @code{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
+and off with a compile-time directive. You must use the macro name we
specify for that part. @xref{Problem 1-4 Advanced Scheduler}, for
details.
#include <inttypes.h>
@dots{}
int32_t value = @dots{};
-printf ("value=%08"PRId32"\n");
+printf ("value=%08"PRId32"\n", value);
@end example
@noindent
The @samp{%} is not supplied by the @code{PRI} macros. As shown