From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12347 invoked by alias); 21 Mar 2007 09:28:23 -0000 Received: (qmail 12332 invoked by uid 22791); 21 Mar 2007 09:28:20 -0000 X-Spam-Check-By: sourceware.org Received: from javad.com (HELO javad.com) (216.122.176.236) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 21 Mar 2007 09:28:16 +0000 Received: from osv ([87.236.81.130]) by javad.com (8.11.6/8.11.0) with ESMTP id l2L9SBU17142; Wed, 21 Mar 2007 09:28:11 GMT (envelope-from s.organov@javad.com) Received: from osv by osv with local (Exim 4.63) (envelope-from ) id 1HTx6z-0005tG-E0; Wed, 21 Mar 2007 12:28:05 +0300 From: Sergei Organov To: "Paul D. DeRocco" Cc: "eCos Discuss" References: <01cf01c76b52$367b77a0$8d7ba8c0@PAULD> Date: Wed, 21 Mar 2007 09:28:00 -0000 In-Reply-To: <01cf01c76b52$367b77a0$8d7ba8c0@PAULD> (Paul D. DeRocco's message of "Tue, 20 Mar 2007 17:45:24 -0700") Message-ID: <87bqin54ka.fsf@javad.com> User-Agent: Gnus/5.110006 (No Gnus v0.6) XEmacs/21.4.19 (linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: [ECOS] Re: eCos C++ API X-SW-Source: 2007-03/txt/msg00128.txt.bz2 "Paul D. DeRocco" writes: > Are the C++ objects on which eCos is based supposed to be invisible to the > programmer, so that the designers of eCos can change them at will? Or is it > reasonable for a programmer writing an application in C++ to directly use > the underlying eCos C++ objects? Since everything else in my application is > in C++, I'd much rather do the latter, for instance creating a thread > directly as a Cyg_Thread instead of declaring a cyg_thread and having to > call cyg_thread_create. > >From practical point of view, the C++ objects didn't change incompatibly from the time I started to use them back in around 2001/2002. Yes, my application is in C++ and it seems to be plain overhead to use C-wrappers over C++ eCos kernel in C++ applications. Though I do use my own C++ wrappers over eCos C++ kernel, so even if eCos classes change, the changes to the application will be localized. > I assume kernel.hxx is the appropriate header to include, instead of kapi.h, > right? Is there any documentation on what might be part of the "official" > C++ API, or am I on my own in judging which things in the headers are likely > to be stable and which might disappear in a later version? Massa's book says > there isn't any standard, but that's four years old. There is still no "official" standard eCos C++ API. You will need to include headers that contain required declarations. For example, my mutex wrapper contains: #include #include -- Sergei. -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss