From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3174 invoked by alias); 13 Jun 2005 09:24:01 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 3150 invoked by uid 22791); 13 Jun 2005 09:23:56 -0000 Received: from anchor-post-35.mail.demon.net (HELO anchor-post-35.mail.demon.net) (194.217.242.85) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 13 Jun 2005 09:23:56 +0000 Received: from calivar.demon.co.uk ([83.104.54.243] helo=xl5.calivar.com) by anchor-post-35.mail.demon.net with esmtp (Exim 4.42) id 1Dhl70-000FXZ-GE; Mon, 13 Jun 2005 09:20:06 +0000 Received: from xl5.calivar.com (localhost [127.0.0.1]) by xl5.calivar.com (Postfix) with ESMTP id 0603915840; Mon, 13 Jun 2005 10:23:52 +0100 (BST) To: Fabian Scheler Cc: Bart Veer , ecos-discuss@ecos.sourceware.org References: <69dd805e050610140534b5250c@mail.gmail.com> <20050611132234.6AF8765C057@smtp.ecoscentric.com> <69dd805e05061300412b58888@mail.gmail.com> From: Nick Garnett Original-Sender: nickg@ecoscentric.com Date: Mon, 13 Jun 2005 09:24:00 -0000 In-Reply-To: <69dd805e05061300412b58888@mail.gmail.com> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [ECOS] Dangerous method: Cyg_SchedulerImplementation::set_idle_thread(Cyg_Thread* thread)? X-SW-Source: 2005-06/txt/msg00085.txt.bz2 Fabian Scheler writes: > Hi, > > > This function is not part of the exported API: there is no C > > equivalent in kapi.h, nor is there any documentation. It is intended > > only for use within the kernel, and only gets used during system > > initialization. > > Ok, I agree that the eCos-user is intended to use the C-API, but he is > not forbidden to use the C++-API, is he? And if this method is used > for initialization pruposes only, why is it declared public? The C++ public/protected/private thing is fairly crude. It doen't allow us to distinguish between public-in-the-kernel-only and public-to-everyone. There's only so much we can do to keep kernel interfaces secure. -- Nick Garnett eCos Kernel Architect http://www.ecoscentric.com The eCos and RedBoot experts -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss