Computer Old Farts Forum
 help / color / mirror / Atom feed
From: imp at bsdimp.com (Warner Losh)
Subject: [COFF] On having a slash
Date: Mon, 13 Apr 2020 08:23:49 -0600	[thread overview]
Message-ID: <CANCZdfqPmcYv7js5Xb9iyX1-GegcowiAF55gVFfMFxSbbSuWBA@mail.gmail.com> (raw)
In-Reply-To: <b1927f055d9e69d230ac6869bc38c1d8@firemail.de>

On Mon, Apr 13, 2020 at 8:22 AM Thomas Paulsen <thomas.paulsen at firemail.de>
wrote:

> 'Since the 1/l and 0/O were displayed
> identically, the programmers didn't find the prank funny.  Our
> instructor said as he traveled the US training groups, he hoped he would
> find the guy.  10 or 15 years later he was still more than a tad angry.
> All for lack of slashes and serifs.'
>
> the 1/l/i confusion was a real problem in those days when I saw numberless
> frustrated programmers whose programs did anything but the expected.
>

There's many obfuscation tools for 'C' that existed back in the day which
did the above automatically. I've had the displeasure to debug code run
through that for which the original source has been lost...  "Pleasure" ...
right. I'll go with that since this is still polite company.

Warner
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200413/73fb45e5/attachment.html>


  reply	other threads:[~2020-04-13 14:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-13  9:01 dave
2020-04-13 11:30 ` david
2020-04-13 12:38   ` clemc
2020-04-13 14:10     ` mike.ab3ap
2020-04-13 14:21       ` thomas.paulsen
2020-04-13 14:23         ` imp [this message]
2020-04-13 12:53   ` paul
2020-04-13 14:12     ` imp
2020-04-13 15:29   ` krewat
2020-04-13 15:40     ` pdagog
2020-04-13 13:21 ` thomas.paulsen
2020-04-13 13:23 ` cym224
2020-04-13 13:36   ` 
2020-04-13 17:35   ` paul
2020-04-13 22:09     ` dave
2020-04-14 13:34       ` dfawcus+lists-coff
2020-04-14 14:23         ` gdmr
2020-04-13 22:12     ` krewat
2020-04-13 23:21       ` dave
2020-04-14  0:12 ` grog
2020-04-14  2:57 ` paul.allan.palmer
2020-04-13 15:14 rudi.j.blom

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=CANCZdfqPmcYv7js5Xb9iyX1-GegcowiAF55gVFfMFxSbbSuWBA@mail.gmail.com \
    --to=coff@minnie.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).