The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Winalski <paul.winalski@gmail.com>
To: TUHS <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] C++ / Kernel
Date: Sun, 26 Aug 2018 12:34:34 -0400	[thread overview]
Message-ID: <CABH=_VT5Yi-6uRz_-045cmf-4kbgTSHZhsCLLracoFXNDwSAYQ@mail.gmail.com> (raw)
In-Reply-To: <20180824181522.2nrUS%steffen@sdaoden.eu>

On 8/24/18, Steffen Nurpmeso <steffen@sdaoden.eu> wrote:
>
> Though even more unfortunate i am, since this union trick is often
> the only way to be able to do proper a.k.a. allowed type
> conversion, where the standard text forbids something quick and
> easy, casting of or to function pointers in C++ comes to mind
> spontaneously.  (The linked story also tries to go via (char*) to
> a desired type, but the compiler seems to be too neat.  And even
> if this is a bug, of course...)

One of the complaints about DEC's C99 compiler for Ultrix was that it
was too didactic in its enforcement of the C99 standard.  One customer
called it the Rush Limbough of compilers, because it was extremely
conservative and you couldn't argue with it.

Function pointers can be tricky, as they might not be simple pointers
to a sequence of instructions.  On Itanium, for example, a C
pointer-to-function points to a descriptor for the function, not the
function code itself.

-Paul W.

  reply	other threads:[~2018-08-26 16:34 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-23 14:42 ron
2018-08-23 17:24 ` Clem Cole
2018-08-23 20:21 ` Bakul Shah
2018-08-23 22:17   ` ron
2018-08-23 22:28     ` Nevin Liber
2018-08-23 22:48       ` Clem Cole
2018-08-23 23:14     ` Steffen Nurpmeso
2018-08-24 14:13       ` Steffen Nurpmeso
2018-08-24 14:32         ` ron
2018-08-24 18:15           ` Steffen Nurpmeso
2018-08-26 16:34             ` Paul Winalski [this message]
2018-08-27 16:31               ` Steffen Nurpmeso
2018-08-24  1:41     ` Bakul Shah
2018-08-24 10:41       ` Pete Turnbull
2018-08-24 12:17       ` ron
2018-08-24 18:36         ` Bakul Shah
2018-08-24 18:38           ` ron
2018-08-24  1:58     ` Dan Cross
2018-08-24  3:04       ` Clem cole
2018-08-24 14:01         ` Dan Cross
2018-08-24 13:22 ` Derek Fawcus
2018-08-24 16:59   ` Steffen Nurpmeso
2018-08-23 23:29 Noel Chiappa
2018-08-23 23:42 ` ron
2018-08-24  0:30   ` Clem Cole
2018-08-24  2:05     ` Bakul Shah
2018-08-24 12:21     ` ron
2018-08-24  1:27 Noel Chiappa
2018-08-24  2:52 ` Clem cole
2018-08-24  7:30 Paul Ruizendaal

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='CABH=_VT5Yi-6uRz_-045cmf-4kbgTSHZhsCLLracoFXNDwSAYQ@mail.gmail.com' \
    --to=paul.winalski@gmail.com \
    --cc=tuhs@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).