popt competes for mind share with getopt, and particularly with GNU getopt_long, the Debian added borkedness (jmnsho).
Should I add a getopt(3)/getopt_long(3) wrapper onto popt to lower the barrier to converting from getopt_long(3)? I personally don't care a bit because I use popt instead of getopt_long(3) all the time and everywhere. But the wrapper (with AutoFu disablers) is trivially arranged if there is interest. (Note: one thing that popt __DOES__ need is the ability to per-executable option persistent preference settings. But that can be done in many ways, not just the way that getopt_long(3) implements). 73 de Jeff ______________________________________________________________________ POPT Library http://rpm5.org Developer Communication List popt-devel@rpm5.org
