From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27521 invoked by alias); 7 Sep 2007 11:32:16 -0000 Received: (qmail 27512 invoked by uid 22791); 7 Sep 2007 11:32:15 -0000 X-Spam-Check-By: sourceware.org Received: from elasmtp-banded.atl.sa.earthlink.net (HELO elasmtp-banded.atl.sa.earthlink.net) (209.86.89.70) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 07 Sep 2007 11:32:07 +0000 Received: from [76.167.204.177] (helo=PAULD) by elasmtp-banded.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1ITc4D-0004dY-FI for ecos-discuss@ecos.sourceware.org; Fri, 07 Sep 2007 07:32:05 -0400 From: "Paul D. DeRocco" To: "'ecos-discuss'" Date: Fri, 07 Sep 2007 11:32:00 -0000 Message-ID: <00a701c7f142$b4e60ee0$887ba8c0@PAULD> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook, Build 10.0.6822 In-Reply-To: <20070907091910.GJ32192@lunn.ch> X-ELNK-Trace: bd7d5d4e6f8f652c74cfc7ce3b1ad11381c87f5e51960688c97c52c9d384cc339a29ebc45088d71c350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-IsSubscribed: yes 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: RE: [ECOS] ecos kernel modification and kapidata X-SW-Source: 2007-09/txt/msg00032.txt.bz2 > From: Andrew Lunn >=20 > There is nothing to stop you calling the C++ API, but we=20 > don't recommend it. The C API is documented and frozen. The=20 > C++ is not documented and not frozen, it can and does change.=20 >=20 > So we reserve the right to break your application if you use=20 > the C++ API :-) Unfortunately, it's not generally possible to create synchronization objects comparable to the built-in ones without writing in C++, and the set provided is pretty limited. You need to access things like thread_queue objects, and call member functions like set_sleep_reason, get_wake_reason, etc. I think that, since eCos is written in C++, it should be documented primarily in C++, and people should be encouraged to use the C++ API. The C API should be provided as an optional layer, like Posix or uItron. --=20 Ciao, Paul D. DeRocco Paul mailto:pderocco@ix.netcom.com=20 -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss