The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "John P. Linderman" <jpl.jpl@gmail.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>, jnc'@mercury.lcs.mit.edu
Subject: Re: [TUHS] Cryptic Unix Commands
Date: Wed, 5 Sep 2018 12:12:15 -0400	[thread overview]
Message-ID: <CAC0cEp_yYYhwi1SinvsHeT=WhismC7gsM3mBnBTpsX2FmcS6Zg@mail.gmail.com> (raw)
In-Reply-To: <20180905154435.103E118C0A0@mercury.lcs.mit.edu>

[-- Attachment #1: Type: text/plain, Size: 532 bytes --]

On Wed, Sep 5, 2018 at 11:44 AM, Noel Chiappa <jnc@mercury.lcs.mit.edu>
wrote:

>     > From: Norman Wilson
>
>     > It is just plain wrong to code
>     >  kill(9, pid)
>
> _All_ uses of magic numbers in numeric form are wrong!
>
>         Noel
>

I completely agree, although you can do worse. A junior programmer I worked
with at MIT wrote (in IBM assembler)

twelv dc 10

(I probably have the syntax wrong, but he was declaring the value of
symbolic name 'twelv' to be 10). I have no idea why he did this. He didn't
last long.

[-- Attachment #2: Type: text/html, Size: 1305 bytes --]

  reply	other threads:[~2018-09-05 16:12 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-05 15:44 Noel Chiappa
2018-09-05 16:12 ` John P. Linderman [this message]
2018-09-05 16:45 ` Kurt H Maier
  -- strict thread matches above, loose matches on Subject: below --
2018-09-05 15:04 Norman Wilson
2018-09-05 15:42 ` Chet Ramey
2018-08-24 16:06 [TUHS] Research UNIX on the AT&T 3B2? Clem Cole
2018-08-27 15:54 ` Mary Ann Horton
2018-08-27 17:33   ` Clem Cole
2018-08-28  0:24     ` Dave Horsfall
2018-08-28  0:30       ` Larry McVoy
2018-08-28  6:01         ` arnold
2018-08-28 22:33           ` Dave Horsfall
2018-08-29  0:36             ` Harald Arnesen
2018-08-29  1:06               ` Dave Horsfall
2018-08-29  3:23                 ` Theodore Y. Ts'o
2018-08-29  4:36                   ` [TUHS] Cryptic Unix Commands Warren Toomey
2018-08-29 16:13                     ` Jeremy C. Reed
2018-08-29 22:03                     ` Dave Horsfall
2018-08-29 22:09                       ` Grant Taylor via TUHS
2018-08-29 22:21                         ` William Pechter
2018-08-29 23:04                           ` Grant Taylor via TUHS
2018-08-29 23:38                             ` Larry McVoy
2018-08-30  3:59                             ` William Pechter
2018-08-29 22:31                       ` Dan Mick
2018-08-29 23:00                         ` Grant Taylor via TUHS
2018-08-30  8:28                           ` Dave Horsfall
2018-08-30 11:06                       ` ron
2018-08-30 11:35                         ` John P. Linderman
2018-08-30 13:24                         ` Clem Cole
2018-08-30 14:31                           ` William Pechter
2018-08-30 15:01                             ` Clem Cole
2018-08-30 15:22                               ` Warner Losh
2018-08-30 16:11                                 ` William Pechter

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='CAC0cEp_yYYhwi1SinvsHeT=WhismC7gsM3mBnBTpsX2FmcS6Zg@mail.gmail.com' \
    --to=jpl.jpl@gmail.com \
    --cc=jnc'@mercury.lcs.mit.edu \
    --cc=jnc@mercury.lcs.mit.edu \
    --cc=tuhs@tuhs.org \
    /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).