From 4142d6dcf0e7f8d4f348c11b4cc5066db3261c63 Mon Sep 17 00:00:00 2001 From: Ben Pfaff Date: Mon, 18 Oct 2004 18:39:11 +0000 Subject: [PATCH] Warn that coding style costs points. --- doc/standards.texi | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/standards.texi b/doc/standards.texi index 7af266e..a13058a 100644 --- a/doc/standards.texi +++ b/doc/standards.texi @@ -39,9 +39,10 @@ follows the @uref{http://www.gnu.org/prep/standards_toc.html, , GNU Coding Standards}. We encourage you to follow the applicable parts of them too, especially chapter 5, ``Making the Best Use of C.'' Using a different style won't cause actual problems, but it's ugly to see -gratuitous differences in style from one function to another. +gratuitous differences in style from one function to another. If your +code is too ugly, it will cost you points. -Pintos comments sometimes refer to outside standards or +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 this documentation (@pxref{References}). -- 2.30.2