summaryrefslogtreecommitdiffstats
path: root/share/man/man9/intro.9
diff options
context:
space:
mode:
authorschweikh <schweikh@FreeBSD.org>2001-07-14 19:41:16 +0000
committerschweikh <schweikh@FreeBSD.org>2001-07-14 19:41:16 +0000
commit511e378b14868fd06fca565a7db84b7080fdbcb7 (patch)
treefb1031efffc2846e7cacb61180a01c78ece1c3e9 /share/man/man9/intro.9
parentb855a121e272a07bd83ce7b51f776e73d7412cf4 (diff)
downloadFreeBSD-src-511e378b14868fd06fca565a7db84b7080fdbcb7.zip
FreeBSD-src-511e378b14868fd06fca565a7db84b7080fdbcb7.tar.gz
Removed whitespace at end-of-line; no content changes. I simply did
cd src/share; find man[1-9] -type f|xargs perl -pi -e 's/[ \t]+$//' BTW, what editors are the culprits? I'm using vim and it shows me whitespace at EOL in troff files with a thick blue block... Reviewed by: Silence from cvs diff -b MFC after: 7 days
Diffstat (limited to 'share/man/man9/intro.9')
-rw-r--r--share/man/man9/intro.912
1 files changed, 6 insertions, 6 deletions
diff --git a/share/man/man9/intro.9 b/share/man/man9/intro.9
index 27ad145..0d927e9 100644
--- a/share/man/man9/intro.9
+++ b/share/man/man9/intro.9
@@ -45,11 +45,11 @@ Yes please.
.Pp
We would like all code to be fully prototyped.
.Pp
-If your code compiles cleanly with
+If your code compiles cleanly with
.Nm cc
-.Ar -Wall
+.Ar -Wall
we would feel happy about it.
-It is important to understand that this isn't a question of just shutting up
+It is important to understand that this isn't a question of just shutting up
.Nm cc ,
it is a question about avoiding the things it complains about.
To put it bluntly, don't hide the problem by casting and other
@@ -61,7 +61,7 @@ It isn't generally applied though.
We would appreciate if people would pay attention to it, and at least not
violate it blatantly.
.Pp
-We don't mind it too badly if you have your own style, but please make
+We don't mind it too badly if you have your own style, but please make
sure we can read it too.
.Pp
Please take time to read
@@ -69,7 +69,7 @@ Please take time to read
for more information.
.Sh NAMING THINGS
Some general rules exist:
-.Bl -enum
+.Bl -enum
.It
If a function is meant as a debugging aid in DDB, it should be enclosed
in
@@ -80,7 +80,7 @@ in
.Ed
.Pp
And the name of the procedure should start with the prefix
-.Li DDB_
+.Li DDB_
to clearly identify the procedure as a debugger routine.
.El
.Sh SCOPE OF SYMBOLS
OpenPOWER on IntegriCloud