From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: [9fans] fix // comments
Date: Sun, 9 Aug 2009 09:29:31 -0400 [thread overview]
Message-ID: <f1171d12349ecdc4c6e4fc93b271dc01@quanstro.net> (raw)
/n/sources/contrib/quanstro/bcmt will turn // comments
into style(6)-approved comments. it deals with end-of-line
comments, single comments and block comments. it's
ment to be used from acme so it is likely unfit for scripting.
for example,
// Ignore network errors here. If we fail during
// synchronization, the next alarm will pick up
// the error.
gets converted to
/*
* Ignore network errors here. If we fail during
* synchronization, the next alarm will pick up
* the error.
*/
and
// Read the header.
if ((len = readn(netfd, &b->hdr, sizeof(Hdr))) <= 0) {
to
/* Read the header. */
if ((len = readn(netfd, &b->hdr, sizeof(Hdr))) <= 0) {
- erik
reply other threads:[~2009-08-09 13:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f1171d12349ecdc4c6e4fc93b271dc01@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).