    <rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/">
     <channel>
        <title>ACCU  :: The Wall</title>
        <link>https://members.accu.org/index.php/articles/974</link>
        <description>Professionalism in Programming</description>
        <dc:language>en-us</dc:language> 
        <dc:creator>Administrator</dc:creator> 
        <admin:generatorAgent rdf:resource="http://www.xaraya.org" /> 
        <admin:errorReportsTo rdf:resource="mailto:webeditor@accu.org" />
       <sy:updatePeriod>hourly</sy:updatePeriod>
       <sy:updateFrequency>1</sy:updateFrequency>
       <docs>http://backend.userland.com/rss</docs>




<div class="xar-mod-head"><span class="xar-mod-title">Letters to the Editor + CVu Journal Vol 12, #1 - Jan 2000</span></div>

<table border="0" cellpadding="1" cellspacing="0">
    <tbody>
    <tr>
        <td valign="top">
            Browse in :
       </td>
       <td valign="top">

                                            <a href="https://members.accu.org/index.php/articles/">All</a>

                     &gt;                         <a href="https://members.accu.org/index.php/articles/c184/">Journal Columns</a>

                     &gt;                         <a href="https://members.accu.org/index.php/articles/c186/">LettersEditor</a>
<br />

                                            <a href="https://members.accu.org/index.php/articles/">All</a>

                     &gt;                         <a href="https://members.accu.org/index.php/articles/c76/">Journals</a>

                     &gt;                         <a href="https://members.accu.org/index.php/articles/c77/">CVu</a>

                     &gt;                         <a href="https://members.accu.org/index.php/articles/c128/">121</a>
<br />

                                            <a href="https://members.accu.org/index.php/articles/c186-128/">Any of these categories</a>

                    -                        <a href="https://members.accu.org/index.php/articles/c186+128/">All of these categories</a>
<br />
</td>
   </tr>
   </tbody>
</table>




<div class="xar-error">
   <p>
 <strong>Note:</strong> when you create a new publication type,
the articles module will automatically use the templates
<em>user-display-[publicationtype].xt</em>
and <em>user-summary-[publicationtype].xt</em>.
If those templates do not exist when you try to preview or display a new article,
you'll get this warning :-)  Please place your own templates in themes/<em>yourtheme</em>/modules/articles . The templates will get the extension .xt there. </p>
</div>
<div class="xar-norm xar-standard-box-padding">
   <h1><strong>Title:</strong>&nbsp;The Wall</h1>
<p><strong>Author:</strong>&nbsp;</p>
<p>
<strong>Date:</strong> 08 January 2000 13:15:34 +00:00 or Sat, 08 January 2000 13:15:34 +00:00</p>
<p><strong>Summary:</strong>&nbsp;</p>
<p><strong>Body:</strong>&nbsp;<div class="sect1" lang="en">
<div class="titlepage">
<h2><a name="d0e24" id="d0e24"></a>Syntax
Highlighting</h2>
</div>
<p>Dear Francis,</p>
<p>I was interested in Richard Blundell's comments on code
legibility in C Vu 11.6, when he describes the difficulties in
speed-reading code with long identifiers and symbols. What is
needed is for the symbols to stand out differently, and for this
reason (among others) I very much prefer syntax highlighting in the
editor.</p>
<p>Syntax highlighting can be done with either fonts or colours, or
both. If you have colour vision then you should find that colours
work better, so long as they are chosen such that the contrast is
good. Font highlighting has the advantage of being more easily
printed, although much depends on the choice of fonts.</p>
<p>GNU Emacs can do both, and it calls them both &quot;font-lock&quot; (I
find it best on &quot;maximum decoration&quot;). I have not yet found out how
to customise the colours that are used for the various parts of the
language, but enabling font-lock is simply a matter of putting the
following in your .emacs file:</p>
<pre class="literallayout">
  (setq-default font-lock-auto-fontify t)
  (setq-default font-lock-use-fonts nil)
  (setq-default font-lock-use-colors t)
  (setq-default font-lock-maximum-decoration t)
  (require 'font-lock)
</pre>
<p>(Of course, xemacs has it all in the menus somewhere.) By the
way, that enables syntax highlighting for not only C and C++ but
also most of the other languages that emacs knows about, such as
SGML/HTML, Lisp, Perl, Prolog, sh, Outline documentation, and
numerous others (although the syntax highlighting is better in some
than in others).</p>
<p>Another common program that does syntax highlighting is a2ps, a
Unix &quot;pretty printer&quot;. On Windows, many IDEs are capable of it.
Other benefits of syntax highlighting include keyword highlighting
(which can reduce problems with miss-spelt keywords), and, when you
are used to it, the quick recognition of idioms (such as loops)
without having to read them. This is very useful if you need large
print, since you can &quot;zoom out&quot; and see more of the code when you
are only navigating it.</p>
<p>I urge all readers to try syntax highlighting if you have not
already done so, to see if it is for you. Different people will
find different results, but it's one of those things that you might
as well try. It was not invented just for the visually
impaired.</p>
<p>Silas S Brown <a href="http://epona.ucam.org/~ssb22" target=
"_top">http://epona.ucam.org/~ssb22</a></p>
<p class="c3"><span class="remark">I like that zoom out idea as
being something that allows you to see larger scale source code
patterns.</span></p>
</div>
</p>
<p><strong>Notes:</strong>&nbsp;</p>
<p><em>More fields may be available via dynamicdata ..</em></p>
</div>
</channel>
</rss>
