Re: C++ in the kernel
- From: "Poul-Henning Kamp" <phk@xxxxxxxxxxxxxx>
- Date: Sat, 27 Oct 2007 11:19:37 +0000
In message <472317D7.8010406@xxxxxxxxxxxxxxx>, Bruce M Simpson writes:
I could not find any reference to this discussion in a mailing list
search. I did read the article at: http://wiki.freebsd.org/K. It sounds
like a new and interesting approach to a C-like language (* see footnote).
However, that was not the original topic of my thread, which is to gauge
interest for C++ runtime support in FreeBSD and if anyone is already
doing this.
One major problem I see about a C++ runtime, is that it puts even
worse constraints on our compiler situation, raising the bar
significantly for any non GPLv3 compiler we might consider.
K, as envisioned, has the opposite effect, it gives us a layer of
isolation from the backend C-compiler, a layer which we have 100%
control with, and can bend to our requirements, rather than have
to live with the sometimes arbitrary and often insensitive choices
by the GCC crowd.
Absent actual code for a K compiler, this is largely a philosophical
discussion with little applicability, but the strategic impact of
supporting C++ in the kernel should not be overlooked just because
of that detail.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk@xxxxxxxxxxx | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
_______________________________________________
freebsd-arch@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"
- References:
- Re: C++ in the kernel
- From: Bruce M Simpson
- Re: C++ in the kernel
- Prev by Date: Re: C++ in the kernel
- Next by Date: Re: C++ in the kernel
- Previous by thread: Re: C++ in the kernel
- Next by thread: Re: C++ in the kernel
- Index(es):
Relevant Pages
- Re: Microchip Introduces First 16-bit Microcontroller Product Line - the PIC24
... On Sun, 16 Oct 2005, Andreas Schwarz wrote: ... the compiler would have
to generate ... No you do not always need to add a LAYER of software. ... involves
extra work for you. ... (comp.arch.embedded) - RetroForth ANS Layer now available
... I've recently built an Standard Forth compatibility layer for the RetroForth
... compiler. ... (comp.lang.forth) - Re: MPI/Fortran95 incompatibility? Was - Re: Pass by reference in Fortran77 standard?
... No compiler vendor is going to constrain what future compilers might ... >Does
anyone know if the Fortran API for MPI is a layer on top of "base" C (I presume, ... >whatever
language) code -- ala netCDF, where the f90 API is an additional layer on top of ...
(comp.lang.fortran) - Re: when EXACTLY is virtual mechanism used?
... void main coats your mouse with a pasty film. ... well-formed and well-defined
program works "as if" the compiler had followed ... This probably happens in a "virtual
code" layer, ... C++ source and the raw machine language output, ... (comp.lang.cpp)