From owner-freebsd-chat@FreeBSD.ORG Wed Apr 19 07:41:44 2006 Return-Path: X-Original-To: freebsd-chat@freebsd.org Delivered-To: freebsd-chat@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4795416A401 for ; Wed, 19 Apr 2006 07:41:44 +0000 (UTC) (envelope-from dacut@kanga.org) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.200.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA3F643D4C for ; Wed, 19 Apr 2006 07:41:43 +0000 (GMT) (envelope-from dacut@kanga.org) Received: from [127.0.0.1] (c-67-182-132-101.hsd1.wa.comcast.net[67.182.132.101]) by comcast.net (sccrmhc12) with ESMTP id <2006041907414201200frslhe>; Wed, 19 Apr 2006 07:41:43 +0000 Message-ID: <4445E9B6.2090508@kanga.org> Date: Wed, 19 Apr 2006 00:41:42 -0700 From: David Cuthbert User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: freebsd-chat@freebsd.org References: <200604151313.32519.benlutz@datacomm.ch> In-Reply-To: <200604151313.32519.benlutz@datacomm.ch> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 0616-2, 04/18/2006), Outbound message X-Antivirus-Status: Clean Subject: Re: Why is not more FreeBSD software written in C++? X-BeenThere: freebsd-chat@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Non technical items related to the community List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 07:41:44 -0000 Benjamin Lutz wrote: > Why is it that C++ is not used for our programs? The C++ compiler is in the > base and built by default, and the OOP paradigm is a nice one, that many > programmers, especially the younger ones (like me :) ) are probably more > familiar with than the tricks and techniques used in C to achieve good > efficiency. My experience writing commercial C++ code has made me swear that I'll never choose it again when starting a project from scratch. Admittedly, this probably not applicable to a project like FreeBSD, but I'm not about to go changing my bias for just one environment. The problem wasn't in the language itself but in the constantly broken implementations. We were trying to integrate various third-party modules which invariably insisted on using incompatible versions of g++ (or SunPro, or aCC, or xlC, or ...). I still have nightmares about seeing errors related ambiguous name resolution between "std::cout" and "::cout" because two files couldn't agree whether it was "#include " or "#include ". And don't get me started about duplicate or missing template symbols, and that godforsaken SunWS_cache directory which is always out-of-date... These days, I write in C when I need to be close to the machine, and a higher-than-C++-level language otherwise; my personal tonic is Python.