From: steffen@sdaoden.eu (Steffen Nurpmeso)
Subject: [TUHS] // comment in C++
Date: Thu, 09 Feb 2017 14:07:04 +0100 [thread overview]
Message-ID: <20170209130704.XIzNK%steffen@sdaoden.eu> (raw)
In-Reply-To: <9E957EE0-DC6F-4B39-9AF9-CFAE68616CF8@planet.nl>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1890 bytes --]
Paul Ruizendaal <pnr at planet.nl> wrote:
|> On 9 Feb 2017, at 13:12, Michael Kjörling <michael at kjorling.se> wrote:
|> On 8 Feb 2017 17:50 -0500, from ron at ronnatalie.com (Ron Natalie):
|>> Amusingly in the UNIVAC FIELDDATA character set. The @ had the \
|>> value zero
|>> (and was called the master space).
|>
|> 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.
|
|Isn’t it because it is simply the control code + 0100 to arrive at the
|capitals column of the ascii table? (http://www.asciitable.com)
|
|Hence ^@ for NULL and ^[ for ESC.
That is also what i thought and think. The MUA i maintain now
documents (in the next release):
‘\cX’ A mechanism that allows usage of the non-printable
(ASCII and compatible) control codes 0 to 31: to cre‐
ate the printable representation of a control code the
numeric value 64 is added, and the resulting ASCII
character set code point is then printed, e.g., BEL is
‘7 + 64 = 71 = G’. Whereas historically circumflex
notation has often been used for visualization pur‐
poses of control codes, e.g., ‘^G’, the reverse
solidus notation has been standardized: ‘\cG’. Some
control codes also have standardized (ISO 10646, ISO
C) alias representations, as shown above (e.g., ‘\a’,
‘\n’, ‘\t’): whenever such an alias exists S-nail will
use it for display purposes. The control code NUL
(‘\c@’) ends argument processing without producing
further output.
I hope this is correct.
--steffen
next prev parent reply other threads:[~2017-02-09 13:07 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
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 [this message]
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=20170209130704.XIzNK%steffen@sdaoden.eu \
--to=steffen@sdaoden.eu \
/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).