From: David Schollmeyer <dschollmeyer@gmail.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Mbox Class Inlines
Date: Thu, 05 Mar 2009 12:09:00 -0000 [thread overview]
Message-ID: <ed347ce40903040953r128bd2a8t622ea59b3d05ca53@mail.gmail.com> (raw)
I have a question on the usage of the Mbox class. If I just include
<cyg/kernel/mbox.hxx>, I get a compile error that the inline function
Cyg_ThreadQueue::empty() is used but not defined. It appears that
thread.inl is not included. If I look in mbox.hxx, it includes either
mboxt.hxx or mboxt2.hxx to implement the queue depending on the value
of CYGIMP_MBOX_USE_MBOXT_PLAIN. Both of these files say to include
mboxt.inl or mboxt2.inl along with the .hxx file and these .inl files
correctly include thread.inl. If I add an include of
<cyg/kernel/mboxt.inl> in my code everything compiles correctly, but
shouldn't this be done in mbox.hxx due to the MBOXT configuration
option?
David Schollmeyer
--
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:[~2009-03-04 17:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ed347ce40903040953r128bd2a8t622ea59b3d05ca53@mail.gmail.com \
--to=dschollmeyer@gmail.com \
--cc=ecos-discuss@sources.redhat.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).