From: Ben Elliston <bje@au.ibm.com>
To: sid@sources.redhat.com
Subject: Re: Which library for new target specific component?
Date: Fri, 23 Apr 2004 00:00:00 -0000 [thread overview]
Message-ID: <s9rfzavmuuk.fsf@fs.ozlabs.ibm.com> (raw)
In-Reply-To: <4087E58C.3000504@redhat.com>
Dave Brolley <brolley@redhat.com> writes:
> I'm implementing a very specific cache implementation for a target
> we're working on. The component will be abstracted from the current
> cache_component class in sid/components/cache (i.e. it will inherit
> from this class). Which library should this new class belong to?
> Currently I have it in libXXXfamily.la, built from
> sid/components/family/XXX. The effect of this is that libcache.la
> must be loaded before libXXXfamily.la. Should I instead add the code
> to libcache.la (sid/components/cache) so that the libraries are
> independent?
Good question. I think putting it in libcache is fine for the time
being. Presumably it will be some time before the code is contributed
to the public sources?
Ben
prev parent reply other threads:[~2004-04-23 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 15:33 Dave Brolley
2004-04-23 0:00 ` Ben Elliston [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=s9rfzavmuuk.fsf@fs.ozlabs.ibm.com \
--to=bje@au.ibm.com \
--cc=sid@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).