From: usotsuki@buric.co (Steve Nickolas)
Subject: [TUHS] Comments in early Unix systems
Date: Wed, 21 Mar 2018 22:19:12 -0400 (EDT) [thread overview]
Message-ID: <alpine.BSF.2.02.1803212218090.4662@frieza.hoshinet.org> (raw)
In-Reply-To: <20180322014003.2184E18C085@mercury.lcs.mit.edu>
On Wed, 21 Mar 2018, Noel Chiappa wrote:
> Although assembler is often so cryptic, the habit of putting a comment on each
> instruction isn't so unreasonable.
>
> So maybe the sort of comments one sees in assembler code (line-by-line
> descriptions of what's happening; for subroutines, which arguments are in
> which registers; etc) aren't needed in C code, and it took a while for them to
> work out what sort of commenting _was_ appropriate/useful for C code?
I tend to use more comments in my ASM than my C, for what it's worth.
(Most of my coding lately has been in 6502 assembly.)
-uxo.
next prev parent reply other threads:[~2018-03-22 2:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 1:40 Noel Chiappa
2018-03-22 2:19 ` Steve Nickolas [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-23 1:54 Doug McIlroy
2018-03-22 13:49 Doug McIlroy
2018-03-22 14:29 ` Nemo
2018-03-21 14:17 [TUHS] daemons are not to be exorcised Noel Chiappa
2018-03-21 15:03 ` Clem Cole
2018-03-21 16:18 ` Arthur Krewat
2018-03-21 17:28 ` Paul Winalski
2018-03-21 18:04 ` Dan Cross
2018-03-21 19:56 ` Clem Cole
2018-03-21 20:13 ` Paul Winalski
2018-03-21 20:28 ` [TUHS] Comments in early Unix systems Warren Toomey
2018-03-21 20:48 ` Ron Natalie
2018-03-21 22:18 ` William Corcoran
2018-03-21 23:02 ` Clem Cole
2018-03-22 1:31 ` Larry McVoy
2018-03-21 23:17 ` Arthur Krewat
2018-03-21 23:50 ` Larry McVoy
2018-03-22 0:55 ` Mike Markowski
2018-03-22 1:00 ` Larry McVoy
2018-03-21 23:45 ` Warner Losh
2018-03-22 0:31 ` Steve Johnson
2018-03-22 0:58 ` Andy Kosela
2018-03-22 1:27 ` Larry McVoy
2018-03-22 1:59 ` Bakul Shah
2018-03-22 14:46 ` Steve Simon
2018-03-22 15:22 ` ron minnich
2018-03-22 16:22 ` Ron Natalie
2018-03-22 16:32 ` arnold
2018-03-22 20:20 ` Lyndon Nerenberg
2018-03-22 16:33 ` Kurt H Maier
2018-03-23 1:31 ` Charles Anthony
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=alpine.BSF.2.02.1803212218090.4662@frieza.hoshinet.org \
--to=usotsuki@buric.co \
/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).