>>>>> "jek3" == Joseph Kowalski <Joseph.Kowalski at eng.sun.com> writes:
jek3> As the thread points out, we have two libraries (both from AT&T) jek3> called libcmd. Their contents are rather unrelated. Rather than jek3> merging them (which seems very unclean), I'm investigating the jek3> possibility of renaming one. If we renamed the libcmd associated jek3> with ksh, would anybody notice? jek3> Actually, if the answer is "Yes", we have a bigger problem. It is jek3> considered generally bad practice to mix Public and Private APIs jek3> in a library (but its not like we haven't made this error before). While I'll agree that mixing the two libraries is not clean, I had thought that the current proposal was acceptable because it keeps libcmd private. This gets ksh93 into the system for people to start using, while letting the project team have more time to deal with the issues surrounding libcmd. Is that a viable strategy? (If not, why?) mike
