summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-guidelines.tex
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-guidelines.tex')
-rw-r--r--Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-guidelines.tex34
1 files changed, 7 insertions, 27 deletions
diff --git a/Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-guidelines.tex b/Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-guidelines.tex
index 667603494c6..1b032e95779 100644
--- a/Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-guidelines.tex
+++ b/Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-guidelines.tex
@@ -1,10 +1,11 @@
-% $Header: /cvsroot/pgf/pgf/doc/generic/pgf/text-en/pgfmanual-en-guidelines.tex,v 1.1 2005/11/14 17:37:50 tantau Exp $
-
-% Copyright 2005 by Till Tantau <tantau@cs.tu-berlin.de>.
+% Copyright 2006 by Till Tantau
%
-% This program can be redistributed and/or modified under the terms
-% of the GNU Public License, version 2.
-
+% This file may be distributed and/or modified
+%
+% 1. under the LaTeX Project Public License and/or
+% 2. under the GNU Free Documentation License.
+%
+% See the file doc/generic/pgf/licenses/LICENSE for more details.
\section{Guidelines on Graphics}
@@ -23,11 +24,6 @@ by Edward Tufte. While I do not agree with everything written in these
books, many of Tufte's arguments are so convincing that I decided to
repeat them in the following guidelines.
-
-
-
-\subsection{Should You Follow Guidelines?}
-
The first thing you should ask yourself when someone presents a bunch of
guidelines is: Should I really follow these guidelines? This is an
important questions, because there are good reasons not to follow
@@ -53,22 +49,6 @@ general guidelines.
When you are aware of a rule and when you decide that breaking the
rule has a desirable effect, break the rule.
-\item
- Some guidelines are simply \emph{wrong}, but everyone follows them
- out of tradition or is forced to do so. My favorite example is a
- guideline a software company I used to work for has set in a big
- project: All programmers had to declare the parameters of functions
- in \emph{increasing order of size}. So, one-byte
- parameters should come first, then two-byte parameters, and so on.
-
- This guideline is total nonsense. An (arguably) sensible guideline
- is ``parameters must be declared alphabetically'' so that parameters
- are easier to find. Another (arguably) sensible guideline is
- ``parameters must be declared in decreasing order of size'' so that
- less byte-alignment cache misses occur when the stack is
- accessed. The guideline the company used maximized cache misses and
- resulted in a more or less random ordering so that programmers
- constantly had to look up the parameter ordering.
\end{itemize}
So, before you apply a guideline or choose not to apply it, ask