From owner-freebsd-current Thu Jan 18 11:40:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from stox.sa.enteract.com (stox.sa.enteract.com [207.229.132.161]) by hub.freebsd.org (Postfix) with ESMTP id 0C6B437B400 for ; Thu, 18 Jan 2001 11:40:18 -0800 (PST) Received: (from stox@localhost) by stox.sa.enteract.com (8.11.1/8.9.3) id f0IJeBV00960; Thu, 18 Jan 2001 13:40:11 -0600 (CST) (envelope-from stox) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010118072110.A431@puck.firepipe.net> Date: Thu, 18 Jan 2001 13:40:11 -0600 (CST) From: "Kenneth P. Stox" To: Will Andrews Subject: Re: HEADS UP: I386_CPU Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18-Jan-01 Will Andrews wrote: > Well, Warner, I've never done embedded systems. So, tell me, do they > actually use any C++ code in embedded systems? C++ has a rather high > overhead as far as disk space & memory goes. I would imagine that 99%+ > of embedded systems do not use C++ code except perhaps for a very small > amount of the code. FYI, one of the first C++ applications to see the light of day outside of Bell Labs was DMDPI, a debugger for an intelligent graphic terminal ( DMD5620 ). I think that comes close to qualifying as an embedded application. When it is the right tool for the right job, C++ can be the most efficient tool around. When used incorrectly, it can be a nightmare, but then again, so can any language. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message