I'll second shmem'e response: explanatory comments (or just clear code layout with well chosen names for vars and subs) are the best way to draw attention to specific details in code that you want others to read and understand.
Puttering around with what amounts to ASCII-art will be tedious, and well beyond the patience, attention span or mental capacity of many who (try to) post code here. It'll get especially unwieldy when someone feels compelled to use fairly long lines of code with highlighted stuff at the end.
Even though I kinda like dhoss's suggestion to make sure that "highlighting directives" are really nothing more than commented lines in the code, I have to ask: well then, why not just say a few words in those extra comment lines, instead of counting out periods and carets?
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
