From owner-freebsd-chat Tue Mar 5 17:28:15 2002 Delivered-To: freebsd-chat@freebsd.org Received: from falcon.prod.itd.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id 721B737B419 for ; Tue, 5 Mar 2002 17:28:11 -0800 (PST) Received: from pool0228.cvx40-bradley.dialup.earthlink.net ([216.244.42.228] helo=mindspring.com) by falcon.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16iQDj-0006Rj-00; Tue, 05 Mar 2002 17:27:56 -0800 Message-ID: <3C857080.44C5236B@mindspring.com> Date: Tue, 05 Mar 2002 17:27:28 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Kenneth Culver Cc: Nate Williams , "Steve B." , "Eugene L. Vorokov" , freebsd-chat@FreeBSD.ORG Subject: Re: C vs C++ References: <20020305193028.H6706-100000@alpha.yumyumyum.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Kenneth Culver wrote: > I need to learn to say what I mean in a better manner. I've been trying to > say the last comment for this whole thread and just couldn't get it into > words. Thanks. Whatever. The bottom line is that the original poster is being paid by someone to code, and he who pays the piper calls the tune. If he doesn't like it, there are plenty of other companies to work for, and if his manager doesn't like it, there's plenty of people he can hire that *will* do the code in the required language to meet the corporate goals which led to the choice of C++ in the first place. C++ is a good mapping for problems that are subject to object decomposition for solution, and in a design-before-code environemnt (explains why you haven't seen good -- IYO -- Open Source C++ code), it is easier to verify that the code matches the design, and the correctness of the design, as well as being able to use the design document 10 years later to successfully maintain the code. FWIW, the University of Kentucky did a Bell Labs/USL sponsoered OS research project called "Choices", written in C++. It had a stacking VFS architecture implemented using a pure virtual base class and inheritance. In the demo for this code, I saw extended attributes and ACLs added to a filesystem in less than 20 minutes. I have yet to see FreeBSD's stacking VFS architecture handle the cache coherency problem for getpages/putpages correctly, without explicit coherency using read/write to implement the stacking of a top level getpages/putpages, with the associated decoherency in the mmap case not being fixed for the msync() or for the file-and-mmap simultaneous access cases. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message