Date: Mon, 18 Aug 2014 13:36:39 -0400 (EDT) From: Benjamin Kaduk <kaduk@MIT.EDU> To: Stefan Esser <se@freebsd.org> Cc: "arch@freebsd.org" <arch@freebsd.org>, Phil Shafer <phil@juniper.net> Subject: Re: XML Output: libxo - provide single API to output TXT, XML, JSON and HTML Message-ID: <alpine.GSO.1.10.1408181335320.21571@multics.mit.edu> In-Reply-To: <53F1A311.4080707@freebsd.org> References: <201408151613.s7FGDMmt003567@idle.juniper.net> <53F1A311.4080707@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 18 Aug 2014, Stefan Esser wrote:
> Methods discussed so far are e.g.:
>
> - add long option as ARGV[1] (e.g. "--libxo-is-supported")
>
> - use command name prefix ("xo-$CMD" linked to the actual $CMD)
>
> - test for and use different standard file descriptors (XO_STDIN,
> XO_STDOUT, and XO_STDERR) if supported by the command
>
> (I have probably forgotten a few ...)
It seems prudent to consider how well such mechanisms would play with
other libraries attempting to perform similar tricks with regard to
detecting functionality. E.g., the "xo-" prefix can really only be used
by one library at a time.
-Ben
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.GSO.1.10.1408181335320.21571>