home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.lang.c++:11629 alt.sources.d:947 comp.sources.d:1133
- Path: sparky!uunet!cs.utexas.edu!zaphod.mps.ohio-state.edu!sample.eng.ohio-state.edu!purdue!bu.edu!lll-winken!snow.geology.wisc.edu!uakari.primate.wisc.edu!eng.ufl.edu!uflorida!travis!brad
- From: brad@SSD.CSD.HARRIS.COM (Brad Appleton)
- Newsgroups: comp.lang.c++,alt.sources.d,comp.sources.d
- Subject: C++ command-line parsing
- Summary: Options and CmdLine posted on comp.sources.misc
- Keywords: Parsing the command-line in C++
- Message-ID: <9013@travis.csd.harris.com>
- Date: 27 Jul 92 15:39:26 GMT
- Sender: news@travis.csd.harris.com
- Followup-To: comp.lang.c++
- Organization: Harris Computers Systems Division, Fort Lauderdale,FL
- Lines: 21
-
- I have just released on comp.sources.misc, two different C++ class
- libraries for parsing command-line arguments: "Options" and "CmdLine".
- Options is a "bare-bones" package that does just the basics with very
- few bells and whistles thrown in. CmdLine on the other hand is a fully
- object-oriented approach to command-line parsing that does more than
- most of you could ever want. CmdLine also comes with a program named
- "cmdparse" (which is similar to Parseargs) to parse arguments for your
- shell-scripts (including perl and tcl).
-
- If you are the least bit interested (or in need of) C++ command-line
- parsing, then please take a look at one (or both) of these packages.
- Although I have gone through extensive alpha and beta testing, I am
- very anxious to get feedback and comments (constructive of course)
- from the C++ programming community at large.
-
- If you want more info about Options, CmdLine, or Parseargs, then
- please send me e-mail.
- ______________________ "And miles to go before I sleep." ______________________
- Brad Appleton brad@ssd.csd.harris.com Harris Computer Systems
- uunet!travis!brad Fort Lauderdale, FL USA
- ~~~~~~~~~~~~~~~~~~~~ Disclaimer: I said it, not my company! ~~~~~~~~~~~~~~~~~~~
-