Glenn Fowler <gsf at research.att.com> wrote:
> > A libfind based buildin could look this way:
>
> > b_find(int ac, char ** av, FILE *std[], int *interrupted)
>
> the ksh b_*() prototype will not change
If there is no will to allow non ast based libraries to be able to
be be used as ksh builtins, why did then Solaris make place for the name
"libcmd"?
I thought that the intention was to have reusable code.
I did restructure my portability system during the last months and
libschily (libfind is based on libschily) is now implemented in a way
that allows to link any other cleanly build binary against it, if this
other binary does not establish claims that require standard interfaces
to be replaced by ksh internal interfaces.
If the ksh sources are structured in a way that is compatible with
other software, it should be no problem to find a way to let ksh93
use a "standard" libfind. I am willing to create a ksh93 specific b_find()
entry only in case that ksh93 allows me to let the rest of libfind
stay standard software.
If ksh93 is not able to grant this, it looks like a foreign budy in
Solaris....
J?rg
--
EMail:joerg at schily.isdn.cs.tu-berlin.de (home) J?rg Schilling D-13353 Berlin
js at cs.tu-berlin.de (uni)
schilling at fokus.fraunhofer.de (work) Blog:
http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
