-@node Coding Standards, Project Documentation, 4.4BSD Scheduler, Top
+@node Coding Standards
@appendix Coding Standards
-All of you should have taken a class like CS 107, so we expect you to be
-familiar with some set of coding standards such as
-@uref{http://www.stanford.edu/class/cs140/projects/misc/CodingStandards.pdf,
-, CS 107 Coding Standards}. Even if you've taken 107, we recommend
-reviewing that document. We expect code at the ``Peer-Review Quality''
-level described there.
+@localcodingstandards{}
Our standards for coding are most important for grading. We want to
stress that aside from the fact that we are explicitly basing part of
Pintos comments sometimes refer to external standards or
specifications by writing a name inside square brackets, like this:
@code{[IA32-v3a]}. These names refer to the reference names used in
-this documentation (@pxref{References}).
+this documentation (@pxref{Bibliography}).
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
The worst offenders are intentionally not included in the Pintos C
library:
-@table @func
+@table @code
@item strcpy
When used carelessly this function can overflow the buffer reserved
for its output string. Use @func{strlcpy} instead. Refer to
projects / pintos-anon / blobdiff