Roland Mainz writes: > Joseph Kowalski wrote: > > > > Thanks for the explanation, but the reason I'm inquiring is to determine > > if the name libcmd is significant. > > > > As the thread points out, we have two libraries (both from AT&T) called > > libcmd. Their contents are rather unrelated. Rather than merging them > > (which seems very unclean), I'm investigating the possibility of renaming > > one. If we renamed the libcmd associated with ksh, would anybody notice? > > > > Actually, if the answer is "Yes", we have a bigger problem. It is > > considered > > generally bad practice to mix Public and Private APIs in a library (but its > > not like we haven't made this error before). > > The answer is "yes" and it cannot be changed easily without running into > other huge problems (e.g. we just trading one hell for another and I
What are those huge problems? -- 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
