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. If it's something that you'd expect ordinary applications to consume (e.g., Oracle might link against it) without consulting with you directly, and if there'll be a man page, then it's some flavor of Public. If it's something that ordinary applications wouldn't consume without talking with you, then it's Private. It might be Sun Private (meaning "lots of uncontrolled consumers within Solaris"), or Consolidation Private (meaning "just other projects in the same consolidation"), or Project Private. Note that if it's really Public, it must have a man page. > Moreover we will have a bunch of follow-up projects which will quickly > make use of these builtin commands in libshell&&libcmd (e.g. we will > likely see the matching ARC case attack your mailinglist within one or > two weeks after the ksh93 putback is complete... :-) ) ... That argues for Consolidation Private. -- 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
