From: Michael Sweet <mike@easysw.com>
To: printing-architecture@lists.freestandards.org
Cc: "McDonald, Ira" <imcdonald@sharplabs.com>
Subject: Re: [Printing-architecture] Required prefixes for symbols in new OP specs
Date: Wed, 07 Feb 2007 22:16:57 -0500 [thread overview]
Message-ID: <45CA9629.9060509@easysw.com> (raw)
In-Reply-To: <45CA927F.2080306@Sun.COM>
Norm Jacobs wrote:
> ...
> FWIW, this will work for applications linking with libraries
exporting the old interface, but will not solve the problem for loadable
modules that are dlopen()'d and dlsym()'d. In those cases, the shim
method you
> ...
Do we even need to worry about this? Assuming a developer uses this
method, they can still use the old names (which are documented in the
specs) without relying on platform-specific weak linking support.
Regardless, the only time I can see using dlopen() or dlsym() is for
testing for newer versions of libraries at run-time, which will be
using the new naming conventions anyway, right?
--
______________________________________________________________________
Michael Sweet, Easy Software Products mike at easysw dot com
Internet Printing and Publishing Software http://www.easysw.com
next prev parent reply other threads:[~2007-02-08 3:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 17:27 [Printing-architecture] Required prefixes for symbols in new OP specs McDonald, Ira
2007-02-07 19:51 ` Michael Sweet
2007-02-08 3:01 ` Norm Jacobs
2007-02-08 3:16 ` Michael Sweet [this message]
2007-02-07 23:20 ` Olaf Meeuwissen
-- strict thread matches above, loose matches on Subject: below --
2007-02-07 17:36 McDonald, Ira
2007-02-07 23:43 ` Olaf Meeuwissen
2007-02-08 0:07 ` TORATANI Yasumasa
2007-02-07 17:33 McDonald, Ira
2007-02-06 17:04 McDonald, Ira
2007-02-07 0:59 ` Olaf Meeuwissen
2007-02-07 5:19 ` TORATANI Yasumasa
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=45CA9629.9060509@easysw.com \
--to=mike@easysw.com \
--cc=imcdonald@sharplabs.com \
--cc=printing-architecture@lists.freestandards.org \
/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.