David Korn wrote: >> I agree that changing the name as seen by users (via 'builtin -f') is >> a bad idea, but I don't agree that putting plugins in the top level of >> /usr/lib is a good idea, nor do I agree that the user interface must >> always map directly into the internal implementation. >> >> So, I don't see how renaming or moving aside the library will break >> any scripts, so long as 'builtin -f cmd' continues to do exactly the >> same thing. >> >> > > > Most shell plugins should go in .../lib/ksh/plugin.so but libcmd.so > is different since it is not just usable by ksh. We have > nearly 40 other commands that use this library and changing the > location would not work for other systems that also use these commands.
Using the def* interface in libcmd or using the b_* ones that this case adds ? Are any of these 40 other commands similar to ones in Solaris. -- Darren J Moffat
