From: Derek Fawcus <dfawcus+lists-tuhs@employees.org>
To: 'TUHS' <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] C++ / Kernel
Date: Fri, 24 Aug 2018 14:22:44 +0100 [thread overview]
Message-ID: <20180824132244.GA2979@accordion.employees.org> (raw)
In-Reply-To: <10c401d43aef$8be34870$a3a9d950$@ronnatalie.com>
On Thu, Aug 23, 2018 at 10:42:40AM -0400, ron@ronnatalie.com wrote:
>
> > Has anyone experimented with building Unix using C++, to take
> > advantage of strong typing? My guess is no--it would be a Herculean task
> likely to introduce more bugs than it would fix.
I recall that there was an attempt to do this with the Linux kernel,
but that it was abandoned before it was completed, this would have
been pre '98. Probably pre 2.4 Kernel.
I have vague memories of discussions about it on the (kernel) mailing
list at the time, and that it was the original cause of the 'asmlinkage'
annotation on the C level syscalls - basically to turn off C++ name
mangling for when the assembler syscall table referenced the C routines.
DF
next prev parent reply other threads:[~2018-08-24 13:23 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
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 [this message]
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=20180824132244.GA2979@accordion.employees.org \
--to=dfawcus+lists-tuhs@employees.org \
--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).