FreeBSD Bugzilla – Attachment 9975 Details for
Bug 20183
Patches to replaces </>s by something correct
Home
|
New
|
Browse
|
Search
|
[?]
|
Reports
|
Help
|
New Account
|
Log In
Remember
[x]
|
Forgot Password
Login:
[x]
[patch]
file.diff
file.diff (text/plain), 8.58 KB, created by
ue
on 2000-07-25 23:50:01 UTC
(
hide
)
Description:
file.diff
Filename:
MIME Type:
Creator:
ue
Created:
2000-07-25 23:50:01 UTC
Size:
8.58 KB
patch
obsolete
>Index: article.sgml >=================================================================== >RCS file: /home/ncvs/doc/en_US.ISO_8859-1/articles/programming-tools/article.sgml,v >retrieving revision 1.11 >diff -u -r1.11 article.sgml >--- article.sgml 2000/06/14 13:18:43 1.11 >+++ article.sgml 2000/07/25 21:48:27 >@@ -44,10 +44,10 @@ > <para>FreeBSD offers an excellent development environment. > Compilers for C, C++, and Fortran and an assembler come with the > basic system, not to mention a Perl interpreter and classic Unix >- tools such as <command>sed</> and <command>awk</>. If that is >+ tools such as <command>sed</command> and <command>awk</command>. If that is > not enough, there are many more compilers and interpreters in > the Ports collection. FreeBSD is very compatible with standards >- such as <acronym>POSIX</> and <acronym>ANSI</> C, as well with >+ such as <acronym>POSIX</acronym> and <acronym>ANSI</acronym> C, as well with > its own BSD heritage, so it is possible to write applications > that will compile and run with little or no modification on a > wide range of platforms.</para> >@@ -73,8 +73,8 @@ > instruction. This section gives an overview of the two main > ways in which you can give these instructions, or > <quote>commands</quote> as they are usually called. One way >- uses an <firstterm>interpreter</>, the other a >- <firstterm>compiler</>. As human languages are too difficult for >+ uses an <firstterm>interpreter</firstterm>, the other a >+ <firstterm>compiler</firstterm>. As human languages are too difficult for > a computer to understand in an unambiguous way, commands are > usually written in one or other languages specially designed for > the purpose.</para> >@@ -105,10 +105,10 @@ > start if you have not done any programming before. This kind > of environment is typically found with languages like Lisp, > Smalltalk, Perl and Basic. It could also be argued that the >- Unix shell (<command>sh</>, <command>csh</>) is itself an >+ Unix shell (<command>sh</command>, <command>csh</command>) is itself an > interpreter, and many people do in fact write shell > <quote>scripts</quote> to help with various >- <quote>housekeeping</> tasks on their machine. Indeed, part >+ <quote>housekeeping</quote> tasks on their machine. Indeed, part > of the original Unix philosophy was to provide lots of small > utility programs that could be linked together in shell > scripts to perform useful tasks.</para> >@@ -135,16 +135,16 @@ > > <variablelist> > <varlistentry> >- <term><acronym>BASIC</></term> >+ <term><acronym>BASIC</acronym></term> > > <listitem> > <para>Short for Beginner's All-purpose Symbolic > Instruction Code. Developed in the 1950s for teaching > University students to program and provided with every > self-respecting personal computer in the 1980s, >- <acronym>BASIC</> has been the first programming >+ <acronym>BASIC</acronym> has been the first programming > language for many programmers. It's also the foundation >- for <trademark>Visual Basic</>.</para> >+ for <trademark>Visual Basic</trademark>.</para> > > <para>The <ulink > URL="ftp://ftp.FreeBSD.org:pub/FreeBSD/packages/lang/bwbasic-2.10.tgz">Bywater >@@ -184,7 +184,7 @@ > <listitem> > <para>Very popular with system administrators for writing > scripts; also often used on World Wide Web servers for >- writing <acronym>CGI</> scripts.</para> >+ writing <acronym>CGI</acronym> scripts.</para> > > <para>The latest version (version 5) comes with FreeBSD.</para> > </listitem> >@@ -284,7 +284,7 @@ > using separate programs, many commercial compiler makers have > produced Integrated Development Environments > (<acronym>IDE</acronym>s for short). FreeBSD does not have an >- <acronym>IDE</> as such; however it is possible to use Emacs >+ <acronym>IDE</acronym> as such; however it is possible to use Emacs > for this purpose. This is discussed in <xref > linkend="emacs">.</para> > </sect2> >@@ -295,7 +295,7 @@ > > <para>This section deals only with the GNU compiler for C and C++, > since that comes with the base FreeBSD system. It can be >- invoked by either <command>cc</> or <command>gcc</>. The >+ invoked by either <command>cc</command> or <command>gcc</command>. The > details of producing a program with an interpreter vary > considerably between interpreters, and are usually well covered > in the documentation and on-line help for the >@@ -324,9 +324,9 @@ > understandable by humans. Allegedly. > > <footnote> >- <para>To be strictly accurate, <command>cc</> converts the >+ <para>To be strictly accurate, <command>cc</command> converts the > source code into its own, machine-independent >- <firstterm>p-code</> instead of assembly language at >+ <firstterm>p-code</firstterm> instead of assembly language at > this stage.</para> > </footnote></para> > </step> >@@ -361,20 +361,20 @@ > </step> > </procedure> > >- <para>The word <firstterm>compiling</> is often used to refer to >+ <para>The word <firstterm>compiling</firstterm> is often used to refer to > just steps 1 to 4—the others are referred to as >- <firstterm>linking</>. Sometimes step 1 is referred to as >- <firstterm>pre-processing</> and steps 3-4 as >- <firstterm>assembling</>.</para> >+ <firstterm>linking</firstterm>. Sometimes step 1 is referred to as >+ <firstterm>pre-processing</firstterm> and steps 3-4 as >+ <firstterm>assembling</firstterm>.</para> > > <para>Fortunately, almost all this detail is hidden from you, as >- <command>cc</> is a front end that manages calling all these >+ <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> > >- <para>will cause <filename>foobar.c</> to be compiled by all the >+ <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> > >@@ -393,18 +393,18 @@ > isn't.</para> > </footnote></para> > >- <para>There are lots and lots of options for <command>cc</>, which >+ <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 > ones, with examples of how to use them.</para> > > <variablelist> > <varlistentry> >- <term><option>-o <replaceable>filename</replaceable></></term> >+ <term><option>-o <replaceable>filename</replaceable></option></term> > > <listitem> > <para>The output name of the file. If you do not use this >- option, <command>cc</> will produce an executable called >- <filename>a.out</>. >+ option, <command>cc</command> will produce an executable called >+ <filename>a.out</filename>. > > <footnote> > <para>The reasons for this are buried in the mists of >@@ -432,7 +432,7 @@ > </screen> > </informalexample> > >- <para>This will produce an <firstterm>object file</> (not an >+ <para>This will produce an <firstterm>object file</firstterm> (not an > executable) called <filename>foobar.o</filename>. This > can be linked together with other object files into an > executable.</para> >@@ -525,7 +525,7 @@ > > <listitem> > <para>Turn off most, but not all, of the >- non-<acronym>ANSI</> C features provided by >+ non-<acronym>ANSI</acronym> C features provided by > <command>cc</command>. Despite the name, it does not > guarantee strictly that your code will comply to the > standard.</para> >@@ -537,7 +537,7 @@ > > <listitem> > <para>Turn off <emphasis>all</emphasis> >- <command>cc</command>'s non-<acronym>ANSI</> C >+ <command>cc</command>'s non-<acronym>ANSI</acronym> C > features.</para> > </listitem> > </varlistentry> >@@ -1478,7 +1478,7 @@ > listings of core files and sweat over machine code manuals, > but now life is a bit easier. Incidentally, under FreeBSD and > other 4.4BSD systems, a core file is called >- <filename><replaceable>progname</>.core</> instead of just >+ <filename><replaceable>progname</replaceable>.core</filename> instead of just > <filename>core</filename>, to make it clearer which program a > core file belongs to.</para> > >@@ -1771,7 +1771,7 @@ > > <itemizedlist> > <listitem> >- <para>Everything beginning with a <literal>;</> is a comment >+ <para>Everything beginning with a <literal>;</literal> is a comment > and is ignored by Emacs.</para> > </listitem>
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Diff
View Attachment As Raw
Actions:
View
|
Diff
Attachments on
bug 20183
:
9970
|
9971
|
9972
|
9973
|
9974
| 9975