XML Output: libxo - provide single API to output TXT, XML, JSON and HTML

[Marcel Moolenaar]

On Aug 13, 2014, at 10:26 PM, Konstantin Belousov <kostikbel at gmail.com> wrote:
>> 
>> I know ELF "Note" elements can be used to carry vendor-specific
>> data, but have no experience with them.  Would it be reasonable to
>> use them as a means of communicating this information to other bits
>> of software?
> No.

Too extreme.

>> Is FreeBSD using Notes for other information currently?
> Yes, the notes are used to communicate the information required by
> the dynamic linker to correctly activate the image. The mechanism has
> nothing to do with application-specific features, and overloading it for
> that purpose is severe and pointless layering violation. Things should
> not be done just because they could be done.

Too extreme. Life is a lot more subtle. Standards
are as well. There are many examples in the real
world where standards are interpreted a little
more liberal than others may want to. When such
result in (gratuitous) incompatibilities, we all
interpret it as bad. But when it adds real value,
you tend to find it in the next update of the
standard.

> Using the static tagging for the dynamic application properties is wrong
> anyway.  E.g., would you consider the mere fact that the binary is linked
> against your library, as the indication that your feature is supported ?
> If not, how does it differ from the presence of some additional note ?

If we can eliminate static linking for libxo, than
that is definitely easy. Easiest probably. The
question becomes: is it acceptable to not support
static linking for libxo? Or alternatively, is it
acceptable to not be able to check for the feature
on a static executable?

For the first I'm inclined to say yes, but not for
the second.

-- 
Marcel Moolenaar
marcel at xcllnt.net


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.freebsd.org/pipermail/freebsd-arch/attachments/20140814/ae6c0314/attachment.sig>