Re: [snip wacko title]
Garrett Smith wrote:
> David Mark wrote:
>> Event parts.
> This is a very long posting of code.
> It is hard to read the code because it wraps.
> Wrap code at 72 chars so that it is easier to follow.
> If you want others to digest something, don't post such a long post.
> Instead, focus on something smaller. You might choose a format such as:
> I saw a problem [description]
> This is bad because [demonstration/evidence]
> Here is the relevant part [formatted code]
> Recap on problem
I second that, although I am fine with max. 76 characters per line, too.
David's 1874(!) lines posting was filtered out because of its length (so I
would not even read it at first), and as I used the References it is very
hard to follow because code mixes with comments about the code. I have seen
this in other (of his) postings as well.
I think it would be best, if a review of code from outside the newsgroup is
posted, that the code be prefixed with the `| ' character recommended for
third-party quotations or, if the used newsreader does not provide the means
(however all good ones do) or the code is supposed to be tested, that an
unambiguous non-whitespace marker like a line consisting of `-'s clearly
separates the source code from the intermittent comments about it. In the
comments, if a code suggestion is posted, it should probably be indented
with at least two spaces from the left margin so that it can clearly be
distinguished from the original code and the comments. I try to follow that
suggestion in my postings and I have found it to work well.
Use any version of Microsoft Frontpage to create your site.
(This won't prevent people from viewing your source, but no one
will want to steal it.)
-- from <http://www.vortex-webdesign.com/help/hidesource.htm> (404-comp.)