From setantae@submonkey.net  Tue Feb 12 10:52:18 2002
Return-Path: <setantae@submonkey.net>
Received: from relay3-gui.server.ntli.net (relay3-gui.server.ntli.net [194.168.4.200])
	by hub.freebsd.org (Postfix) with ESMTP id 0E9C737B41F
	for <FreeBSD-gnats-submit@freebsd.org>; Tue, 12 Feb 2002 10:52:13 -0800 (PST)
Received: from pc4-card4-0-cust162.cdf.cable.ntl.com
	([80.4.14.162] helo=rhadamanth.private.submonkey.net ident=mailnull)
	by relay3-gui.server.ntli.net with esmtp (Exim 3.03 #2)
	id 16ahzU-0002qN-00
	for FreeBSD-gnats-submit@freebsd.org; Tue, 12 Feb 2002 18:49:20 +0000
Received: from setantae by rhadamanth.private.submonkey.net with local (Exim 3.34 #1)
	id 16ahzU-000Hwu-00
	for FreeBSD-gnats-submit@freebsd.org; Tue, 12 Feb 2002 18:49:20 +0000
Message-Id: <E16ahzU-000Hwu-00@rhadamanth.private.submonkey.net>
Date: Tue, 12 Feb 2002 18:49:20 +0000
From: Ceri <setantae@submonkey.net>
Sender: Ceri <setantae@submonkey.net>
Reply-To: Ceri <setantae@submonkey.net>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: Fixup of the Developer's Handbook, chapter 2
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         34884
>Category:       docs
>Synopsis:       Fixup of the Developer's Handbook, chapter 2
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Feb 12 11:00:01 PST 2002
>Closed-Date:    Wed Feb 13 02:03:39 PST 2002
>Last-Modified:  Wed Feb 13 02:05:32 PST 2002
>Originator:     Ceri <setantae@submonkey.net>
>Release:        FreeBSD 4.5-STABLE i386
>Organization:
>Environment:
System: FreeBSD rhadamanth.private.submonkey.net 4.5-STABLE FreeBSD 4.5-STABLE #0: Thu Feb 7 13:14:41 GMT 2002 setantae@rhadamanth.private.submonkey.net:/usr/obj/usr/src/sys/RHADAMANTH i386


	
>Description:

Various markup patches (use of </> to close elements).
Don't claim to have the latest perl.
Update locations of some packages (gcl will be fixed later when the package
actually builds - maintainer notified).

Ceri

>How-To-Repeat:
	
>Fix:


--- doc/en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml.old	Tue Feb 12 17:30:52 2002
+++ doc/en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml	Tue Feb 12 18:41:45 2002
@@ -144,7 +144,7 @@
 	      for Visual Basic.</para>
 
 	    <para>The <ulink
-		URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/lang/bwbasic-2.10.tgz">Bywater
+		URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/lang/bwbasic-2.20.tgz">Bywater
 		Basic Interpreter</ulink> and the <ulink
 		URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/lang/pbasic-2.0.tgz">Phil
 		Cockroft's Basic Interpreter</ulink> (formerly Rabbit
@@ -163,7 +163,7 @@
 	      languages that were popular at the time.  Instead of
 	      being based on numbers, Lisp is based on lists; in fact
 	      the name is short for <quote>List Processing</quote>.
-	      Very popular in AI (Artificial Intelligence)
+	      Very popular in <acronym>AI</acronym> (Artificial Intelligence)
 	      circles.</para>
 
 	    <para>Lisp is an extremely powerful and sophisticated
@@ -183,7 +183,7 @@
 	      scripts; also often used on World Wide Web servers for
 	      writing <acronym>CGI</acronym> scripts.</para>
 
-	    <para>The latest version (version 5) comes with FreeBSD.</para>
+	    <para>Version 5.005_05 is supplied with FreeBSD.</para>
 	  </listitem>
 	</varlistentry>
 
@@ -198,11 +198,11 @@
 	      abstraction to be used in research work.</para>
 
 	    <para>FreeBSD has packages of the <ulink
-		URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/lang/elk-3.0.tgz">Elk
+		URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/lang/elk-3.0.3.tgz">Elk
 		Scheme Interpreter</ulink>, the <ulink
-		URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/lang/mit-scheme-7.3.tgz">MIT
+		URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/lang/mit-scheme-7.6.0.tgz">MIT
 		Scheme Interpreter</ulink> and the <ulink
-		URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/lang/scm-4e1.tgz">SCM
+		URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/lang/scm-5d4_1.tgz">SCM
 		Scheme Interpreter</ulink>.</para>
 	  </listitem>
 	</varlistentry>
@@ -212,7 +212,7 @@
 
 	  <listitem>
 	    <para><ulink
-		URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/lang/icon-9.0.tgz">The
+		URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/lang/icon-9.4.0.tgz">The
 		Icon Programming Language</ulink>.</para>
 	  </listitem>
 	</varlistentry>
@@ -222,7 +222,7 @@
 
 	  <listitem>
 	    <para><ulink
-		URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/lang/ucblogo-3.3.tgz">Brian
+		URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/lang/ucblogo-4.6.tgz">Brian
 		Harvey's LOGO Interpreter</ulink>.</para>
 	  </listitem>
 	</varlistentry>
@@ -232,7 +232,7 @@
 
 	  <listitem>
 	    <para><ulink
-		URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/lang/python-1.2.tgz">The
+		URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/lang/python-2.1.2.tgz">The
 		Python Object-Oriented Programming
 		Language</ulink></para>
 	  </listitem>
@@ -373,13 +373,13 @@
       <command>cc</command> is a front end that manages calling all these
       programs with the right arguments for you; simply typing</para>
 
-    <screen>&prompt.user; <userinput>cc foobar.c</></screen>
+    <screen>&prompt.user; <userinput>cc foobar.c</userinput></screen>
 
     <para>will cause <filename>foobar.c</filename> to be compiled by all the
       steps above.  If you have more than one file to compile, just do
       something like</para>
 
-    <screen>&prompt.user; <userinput>cc foo.c bar.c</></screen>
+    <screen>&prompt.user; <userinput>cc foo.c bar.c</userinput></screen>
 
     <para>Note that the syntax checking is just that&mdash;checking
       the syntax.  It will not check for any logical mistakes you may
@@ -394,7 +394,7 @@
       </footnote></para>
 
     <para>There are lots and lots of options for <command>cc</command>, which
-      are all in the man page.  Here are a few of the most important
+      are all in the manual page.  Here are a few of the most important
       ones, with examples of how to use them.</para>
 
     <variablelist>
@@ -412,8 +412,8 @@
 	    </footnote></para>
 
 	  <informalexample>
-	    <screen>&prompt.user; <userinput>cc foobar.c</>               <lineannotation>executable is <filename>a.out</></>
-&prompt.user; <userinput>cc -o foobar foobar.c</>     <lineannotation>executable is <filename>foobar</></>
+	    <screen>&prompt.user; <userinput>cc foobar.c</userinput>               <lineannotation>executable is <filename>a.out</filename></lineannotation>
+&prompt.user; <userinput>cc -o foobar foobar.c</userinput>     <lineannotation>executable is <filename>foobar</filename></lineannotation>
 	    </screen>
 	  </informalexample>
 	</listitem>
@@ -552,7 +552,7 @@
 	code</firstterm>.</para>
 
     <para>Generally, you should try to make your code as portable as
-      possible, as otherwise you may have to completely re-write the
+      possible, as otherwise you may have to completely rewrite the
       program later to get it to work somewhere else&mdash;and who
       knows what you may be using in a few years time?</para>
 
@@ -607,8 +607,8 @@
 	    <command>g++</command> on FreeBSD.</para>
 
 	  <informalexample>
-	    <screen>&prompt.user; <userinput>cc -o foobar foobar.cc -lg++</userinput>     <lineannotation>For FreeBSD 2.1.6 and earlier</>
-&prompt.user; <userinput>cc -o foobar foobar.cc -lstdc++</userinput>  <lineannotation>For FreeBSD 2.2 and later</>
+	    <screen>&prompt.user; <userinput>cc -o foobar foobar.cc -lg++</userinput>     <lineannotation>For FreeBSD 2.1.6 and earlier</lineannotation>
+&prompt.user; <userinput>cc -o foobar foobar.cc -lstdc++</userinput>  <lineannotation>For FreeBSD 2.2 and later</lineannotation>
 &prompt.user; <userinput>c++ -o foobar foobar.cc</userinput>
 	    </screen>
 	  </informalexample>
@@ -1377,8 +1377,8 @@
 	on a few of the basic commands.</para>
 
       <para>Finally, if you find its text-based command-prompt style
-	off-putting, there is a graphical front-end for it <ulink
-	  URL="../../../../ports/devel.html">xxgdb</ulink> in the ports
+	off-putting, there is a graphical front-end for it (<ulink
+	  URL="../../../../ports/devel.html">xxgdb</ulink>) in the ports
 	collection.</para>
 
       <para>This section is intended to be an introduction to using
@@ -1460,16 +1460,16 @@
  under certain conditions; type "show copying" to see the conditions.
 There is absolutely no warranty for GDB; type "show warranty" for details.
 GDB 4.13 (i386-unknown-freebsd), Copyright 1994 Free Software Foundation, Inc.
-(gdb) <userinput>break main</>				<lineannotation>Skip the set-up code</>
-Breakpoint 1 at 0x160f: file temp.c, line 9.	<lineannotation><command>gdb</command> puts breakpoint at <function>main()</></>
-(gdb) <userinput>run</>					<lineannotation>Run as far as <function>main()</></>
-Starting program: /home/james/tmp/temp		<lineannotation>Program starts running</>
-
-Breakpoint 1, main () at temp.c:9		<lineannotation><command>gdb</command> stops at <function>main()</></>
-(gdb) <userinput>n</>						<lineannotation>Go to next line</>
-This is my program				<lineannotation>Program prints out</>
-(gdb) <userinput>s</>						<lineannotation>step into <function>bazz()</></>
-bazz (anint=4231) at temp.c:17			<lineannotation><command>gdb</command> displays stack frame</>
+(gdb) <userinput>break main</userinput>				<lineannotation>Skip the set-up code</lineannotation>
+Breakpoint 1 at 0x160f: file temp.c, line 9.	<lineannotation><command>gdb</command> puts breakpoint at <function>main()</function></lineannotation>
+(gdb) <userinput>run</userinput>					<lineannotation>Run as far as <function>main()</function></lineannotation>
+Starting program: /home/james/tmp/temp		<lineannotation>Program starts running</lineannotation>
+
+Breakpoint 1, main () at temp.c:9		<lineannotation><command>gdb</command> stops at <function>main()</function></lineannotation>
+(gdb) <userinput>n</userinput>						<lineannotation>Go to next line</lineannotation>
+This is my program				<lineannotation>Program prints out</lineannotation>
+(gdb) <userinput>s</userinput>						<lineannotation>step into <function>bazz()</function></lineannotation>
+bazz (anint=4231) at temp.c:17			<lineannotation><command>gdb</command> displays stack frame</lineannotation>
 (gdb)</screen>
 
       <para>Hang on a minute! How did <symbol>anint</symbol> get to be
@@ -1477,21 +1477,21 @@
 	<literal>5</literal> in <function>main()</function>? Let's
 	move up to <function>main()</function> and have a look.</para>
 
-      <screen>(gdb) <userinput>up</>					<lineannotation>Move up call stack</>
-#1  0x1625 in main () at temp.c:11		<lineannotation><command>gdb</command> displays stack frame</>
-(gdb) <userinput>p i</>					<lineannotation>Show us the value of <symbol>i</></>
-$1 = 4231					<lineannotation><command>gdb</command> displays <literal>4231</></></screen>
+      <screen>(gdb) <userinput>up</userinput>					<lineannotation>Move up call stack</lineannotation>
+#1  0x1625 in main () at temp.c:11		<lineannotation><command>gdb</command> displays stack frame</lineannotation>
+(gdb) <userinput>p i</userinput>					<lineannotation>Show us the value of <symbol>i</symbol></lineannotation>
+$1 = 4231					<lineannotation><command>gdb</command> displays <literal>4231</literal></lineannotation></screen>
 
       <para>Oh dear! Looking at the code, we forgot to initialise
 	<symbol>i</symbol>.  We meant to put</para>
 
-      <programlisting><lineannotation>&hellip;</>
+      <programlisting><lineannotation>&hellip;</lineannotation>
 main() {
 	int i;
 
 	i = 5;
 	printf("This is my program\n");
-<lineannotation>&hellip</></programlisting>
+<lineannotation>&hellip</lineannotation></programlisting>
 
       <para>but we left the <literal>i=5;</literal> line out.  As we
 	did not initialise <symbol>i</symbol>, it had whatever number
@@ -1788,7 +1788,7 @@
 	quite big!).</para>
 
       <para>The best way to learn Emacs Lisp is to download the <ulink
-	  URL="ftp://prep.ai.mit.edu/pub/gnu/elisp-manual-19-2.4.tar.gz">Emacs
+	  URL="ftp://ftp.gnu.org/old-gnu/emacs/elisp-manual-19-2.4.tar.gz">Emacs
 	  Tutorial</ulink></para>
 
       <para>However, there is no need to actually know any Lisp to get
@@ -2202,11 +2202,11 @@
 	<filename>.emacs</filename> and add a line for whizbang, such
 	as:</para>
 
-      <programlisting><lineannotation>&hellip;</>
+      <programlisting><lineannotation>&hellip;</lineannotation>
 ("\\.lsp$" . lisp-mode)
 ("\\.wiz$" . whizbang-mode)
 ("\\.scm$" . scheme-mode)
-<lineannotation>&hellip;</></programlisting>
+<lineannotation>&hellip;</lineannotation></programlisting>
 
       <para>This means that Emacs will automatically go into
 	<function>whizbang-mode</function> when you edit a file ending
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: murray 
State-Changed-When: Wed Feb 13 02:03:39 PST 2002 
State-Changed-Why:  
I updated this patch to point to the 'Latest' directory on the FTP 
sites, so that we don't have to bother with keeping these version 
numbers updated.  I also evaded the text that talks about the specific 
version of Perl that we use in favor of a more general sentence 
without note of the actual version number in the base system.  That 
sort of thing is too dynamic to keep track of here.  Other than that, 
the patch looks good.  Committed in r1.15.  Thanks for the submission! 


http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34884 
>Unformatted:
