From: Avi Kivity <avi@argo.co.il>
To: "remi.chateauneu@gmail.com" <remi.chateauneu@gmail.com>
Cc: Robert Hancock <hancockr@shaw.ca>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: list.h , list_head and C++
Date: Tue, 27 Feb 2007 18:23:26 +0200 [thread overview]
Message-ID: <45E45AFE.8060501@argo.co.il> (raw)
In-Reply-To: <45E44165.4060608@shaw.ca>
Robert Hancock wrote:
> remi.chateauneu@gmail.com wrote:
>> On Feb 26, 2:26 pm, Robert Hancock <hanco...@shaw.ca> wrote:
>>> remi.chateau...@gmail.com wrote:
>>>> My C++ program needs an intrusive list, possibly with RCU
>>>> capabilities.The data structurelist_head, defined in /usr/include/
>>>> linux/list.h , fits perfectly these needs.
>
I believe boost has a C++ intrusive list, which unlike the kernel's is
completely typesafe.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2007-02-27 16:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1172493644.311389.243780@8g2000cwh.googlegroups.com>
2007-02-26 14:25 ` list.h , list_head and C++ Robert Hancock
[not found] ` <fa.K8OHlwttPU4TDDzMegRRFAIJrxw@ifi.uio.no>
[not found] ` <fa.9RVekJKqUMy1lb5hfYQYDK8VxnE@ifi.uio.no>
[not found] ` <1172571563.228792.208610@h3g2000cwc.googlegroups.com>
2007-02-27 14:34 ` Robert Hancock
2007-02-27 16:23 ` Avi Kivity [this message]
2007-02-27 16:24 ` J.A. Magallón
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=45E45AFE.8060501@argo.co.il \
--to=avi@argo.co.il \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=remi.chateauneu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.