cc: don.cragun at sun.com PSARC-EXT at sac.sfbay.sun.com
Subject: Re: Re: [ksh93-integration-discuss] Re: [osol-arc] Korn Shell 93
Integration [PSARC-EXT/2006/550 Timeout:09/27/2006]
--------
> > From: Glenn Fowler <gsf at research.att.com>
> ...
> > On Thu, 21 Sep 2006 14:24:36 -1000 (HST) Joseph Kowalski wrote:
> > > What about ksh98's libcmd. Why is this considered Public? (If it
> > > is Public, where are the man pages?)
> >
> > save a top level man page that lists the commands foo implemented as
> > extern int b_foo(int _argc, char* const _argv[]);
> > each b_foo self documents and produces its documentation on stderr
> > when invoked with a single option operand of one of
> > --man --html --nroff --usage
> >
> > -- Glenn Fowler -- AT&T Research, Florham Park NJ --
>
> I'm sorry, I can't understand this and I suspect there is something here
> I should understand. Can you be a bit more verbose? Thanks.
>
> To be clear, the issue/question (which I didn't quite ask) is if the
> actual library name (for use as -lcmd to the compilation system) is
> documented anywhere.
>
> - thanks,
>
> - jek3
>
The entry points in the shell libcmd are named b_xxx, where xxx
is a command name and the interface for all of these are
identical. They take an argc, argv, and a context pointer.
b_xxx implements command xxx. If you want a man page for command
xxx, you just run
xxx --man
if you want it displayed on you terminal
xxx --html
if you wnat html, and
xxx --nroff
if you want [nt]roff.
You can also use several other --strings to query specific options.
Thus, it should be simple to generate a man page for libcmd
by writing a shell script.
David Korn
dgk at research.att.com
