public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Nick Garnett <nickg@ecoscentric.com>
To: Fabian Scheler <fabian.scheler@gmail.com>
Cc: Bart Veer <bartv@ecoscentric.com>, ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Dangerous method: Cyg_SchedulerImplementation::set_idle_thread(Cyg_Thread* thread)?
Date: Mon, 13 Jun 2005 09:24:00 -0000	[thread overview]
Message-ID: <m3psuq4nkn.fsf@xl5.calivar.com> (raw)
In-Reply-To: <69dd805e05061300412b58888@mail.gmail.com>

Fabian Scheler <fabian.scheler@gmail.com> 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

      reply	other threads:[~2005-06-13  9:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-10 21:05 Fabian Scheler
2005-06-11 13:22 ` Bart Veer
2005-06-13  7:41   ` Fabian Scheler
2005-06-13  9:24     ` Nick Garnett [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3psuq4nkn.fsf@xl5.calivar.com \
    --to=nickg@ecoscentric.com \
    --cc=bartv@ecoscentric.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=fabian.scheler@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).