The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: lars@nocrew.org (Lars Brinkhoff)
Subject: [TUHS] // comment in C++
Date: Thu, 09 Feb 2017 13:26:54 +0100	[thread overview]
Message-ID: <86inojsg6p.fsf@molnjunk.nocrew.org> (raw)
In-Reply-To: <20170209121204.GJ5418@yeono.kjorling.se> ("Michael \=\?utf-8\?Q\?Kj\=C3\=B6rling\=22's\?\= message of "Thu, 9 Feb 2017 12:12:04 +0000")

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 850 bytes --]

Michael Kjörling <michael at kjorling.se> writes:
> That wouldn't have anything to do with how ^@ is a somewhat common
> representation of 000, would it? (Yes, using octal on purpose.) I've
> always kind of wondered where that notation came from.  That ^A
> through ^Z were representations of 001 through 032 makes more sense.

Look at two slices of the ASCII table:

  0 ^@    64 @
  1 ^A    65 A
  2 ^B    66 B
  3 ^C    67 C
  4 ^D    68 D
  5 ^E    69 E
  6 ^F    70 F
  7 ^G    71 G
  8 ^H    72 H
  9 ^I    73 I
 10 ^J    74 J
 11 ^K    75 K
 12 ^L    76 L
 13 ^M    77 M
 14 ^N    78 N
 15 ^O    79 O
 16 ^P    80 P
 17 ^Q    81 Q
 18 ^R    82 R
 19 ^S    83 S
 20 ^T    84 T
 21 ^U    85 U
 22 ^V    86 V
 23 ^W    87 W
 24 ^X    88 X
 25 ^Y    89 Y
 26 ^Z    90 Z
 27 ^[    91 [
 28 ^\    92 \
 29 ^]    93 ]
 30 ^^    94 ^
 31 ^_    95 _


  reply	other threads:[~2017-02-09 12:26 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-08 18:06 ron minnich
2017-02-08 18:08 ` A. P. Garcia
2017-02-08 18:17 ` arnold
2017-02-08 23:39   ` Steve Johnson
2017-02-08 23:52     ` Dave Horsfall
2017-02-09  2:11       ` Corey Lindsly
2017-02-09  2:46         ` Dave Horsfall
2017-02-09  2:53           ` Corey Lindsly
2017-02-09  4:38           ` Warner Losh
2017-02-09  2:47       ` Steve Nickolas
2017-02-09  4:55         ` Steve Johnson
2017-02-09 11:59           ` Michael Kjörling
2017-02-09 21:56             ` Dave Horsfall
2017-02-10  0:17               ` Dan Cross
2017-02-10  1:58                 ` Dave Horsfall
2017-02-10  2:46                   ` Nemo
2017-02-10  2:49                     ` Dave Horsfall
2017-02-10  9:30                   ` arnold
2017-02-10  9:19               ` arnold
2017-02-09 12:18           ` Brantley Coile
2017-02-09 13:31             ` Nick Downing
2017-02-08 22:45 ` Greg 'groggy' Lehey
2017-02-08 22:50   ` Ron Natalie
2017-02-08 23:22     ` Greg 'groggy' Lehey
2017-02-09 12:12     ` Michael Kjörling
2017-02-09 12:26       ` Lars Brinkhoff [this message]
2017-02-09 14:37         ` Random832
2017-02-09 14:49           ` Random832
2017-02-09 12:31       ` Paul Ruizendaal
2017-02-09 13:07         ` Steffen Nurpmeso
2017-02-08 22:51   ` ron minnich
2017-02-08 23:22     ` Greg 'groggy' Lehey
     [not found] <mailman.204.1486594285.3779.tuhs@minnie.tuhs.org>
2017-02-09  0:03 ` Paul McJones
2017-02-09  2:28   ` Marc Rochkind
2017-02-09 13:11   ` Tony Finch
2017-02-09 14:44 Noel Chiappa
2017-02-09 16:51 ` Steffen Nurpmeso
2017-02-09 19:36   ` Steffen Nurpmeso
2017-02-09 21:14 Doug McIlroy
2017-02-10 17:39 ` Steffen Nurpmeso

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=86inojsg6p.fsf@molnjunk.nocrew.org \
    --to=lars@nocrew.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).