From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964864AbWD0Hz5 (ORCPT ); Thu, 27 Apr 2006 03:55:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964869AbWD0Hz5 (ORCPT ); Thu, 27 Apr 2006 03:55:57 -0400 Received: from lug-owl.de ([195.71.106.12]:59838 "EHLO lug-owl.de") by vger.kernel.org with ESMTP id S964864AbWD0Hz4 (ORCPT ); Thu, 27 Apr 2006 03:55:56 -0400 Date: Thu, 27 Apr 2006 09:55:55 +0200 From: Jan-Benedict Glaw To: linux-kernel@vger.kernel.org Cc: Roman Kononov Subject: Re: C++ pushback Message-ID: <20060427075555.GW25520@lug-owl.de> Mail-Followup-To: linux-kernel@vger.kernel.org, Roman Kononov References: <20060426034252.69467.qmail@web81908.mail.mud.yahoo.com> <20060426200134.GS25520@lug-owl.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ScUgq5oMe+fJq4F1" Content-Disposition: inline In-Reply-To: X-Operating-System: Linux mail 2.6.12.3lug-owl X-gpg-fingerprint: 250D 3BCF 7127 0D8C A444 A961 1DBD 5E75 8399 E1BB X-gpg-key: wwwkeys.de.pgp.net X-Echelon-Enable: howto poison arsenous mail psychological biological nuclear warfare test the bombastical terror of flooding the spy listeners explosion sex drugs and rock'n'roll X-TKUeV: howto poison arsenous mail psychological biological nuclear warfare test the bombastical terror of flooding the spy listeners explosion sex drugs and rock'n'roll User-Agent: Mutt/1.5.9i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org --ScUgq5oMe+fJq4F1 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, 2006-04-26 18:00:52 -0500, Roman Kononov = wrote: > Statement expressions are working fine in g++. The main difficulties are: > - GCC's structure member initialization extensions are syntax > errors in G++: struct foo_t foo=3D{.member=3D0}; Erm, you may want to read the current C standard (C99). This isn't an extension, it's standard. There's a reason why C++ doesn't support that (yet): C++ is a fork of C90 (IIRC), so everything that evolved in C during the years is still missing from C++. > > Anyway, it should all be doable. Not necessarily even very hard. But I= =20 > > doubt it's worth it. >=20 > I think that allowing C++ code to co-exist with the kernel would be a=20 > step forward. You can do with your code whatever you want to:) I think it's just a matter of practice: If C++ code shows up that is less error-prone than C code, doesn't use unverifyable amounts of stack space during constructor runs and is basically _superior_ to C code, that'll find its way into the kernel. But if it's only as good as the C code, then why should anybody bother implementing the neccessary stuff to link C++ code (and to initialize it properly?) MfG, JBG --=20 Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 = _ O _ "Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg = _ _ O f=C3=BCr einen Freien Staat voll Freier B=C3=BCrger" | im Internet! | i= m Irak! O O O ret =3D do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA)= ); --ScUgq5oMe+fJq4F1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFEUHkLHb1edYOZ4bsRAtt9AJ9C+H/OrrtIN/SyAzTGE4NjtSCsYgCaApJP 9qGUrg1KS4kRB7yGkwE5MGs= =gAsE -----END PGP SIGNATURE----- --ScUgq5oMe+fJq4F1--