Glenn Fowler writes: > On Thu, 21 Sep 2006 22:46:49 -0400 James Carlson wrote: > > Roland Mainz writes: > > > I consider it more or less "public" (note that I am always getting the > > > official Sun stabilty terminology wrong - April may correct me if I am > > > causing havic again... :-) ) because the API is stable since many many > > > years and will remain stable as far as I can see into the future. > > > It's not just a matter of whether it will change, but a question of > > whether anyone else should be using the library, and, if so, where > > those other consumers are. > > ast ksh93 -lcmd is a different flavor library > its most common usage would be implicit runtime linking by ksh for > access to the b_xxx builtins rather than explicit compile time linkage > > even applications that explicitly link with -lshell would most likely > only access -lcmd via the implicit ksh93 builtin mechanism > > btw, the ast -ldll library allows ksh93 to refer to -lcmd as > "the cmd plugin named ``cmd''" on all architectures -- it maps > architecure neutral names like "cmd" to architecture specific > shared lib / dll names and directory placement
That still doesn't seem to answer the question. Does anyone outside of this project ever need to link against the new symbols provided in libcmd? Would you want them to do so without consulting with you or your project team? Will you integrate a man page for the library in section 3 describing the functions and symbols provided by the library in enough detail that others may use them? If the answer to those questions is "no," and I suspect it might be, then this is a private library, not public. -- James Carlson, KISS Network <james.d.carlson at sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
