|
From: | felix |
Subject: | Re: [Chicken-users] building readline extension on OSX problem: csc include directory (-I switch) |
Date: | Mon, 30 Aug 2004 21:53:34 +0200 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113 |
address@hidden wrote:
On 30 Aug 2004, Ed Watkeys <address@hidden> wrote:Since the subject came up... I would suggest adhering to the GNU standards regarding command-line options.Seconded.That would mean double dashes for verbose options, and single dashes for single-character optons. Additionally, there would be a verbose option for each single-character one. Here's a useful document:http://www.gnu.org/prep/standards_18.htmlAnd as chicken already supports SRFI-37 ( http://srfi.schemers.org/srfi-37/srfi-37.html ) it should be easy to implement.
I have to admit that I'm no fan of the double hyphen. The only decent way would be to fold SRFI-37 into the core library (utils unit perhaps) and change all programs (csc, chicken, csi, ...) to use the same command-line syntax. For the time being I have changed csc to be slightly more clever with respect to "exploding" unknown options - it checks now whether all characters in an unknown long option are valid short options. This should catch a great many typos on the command line. So, imho single-hyphen long-options are nicer (see gcc, ocaml, ... ;-) but I will change my mind if the majority of people here would prefer GNU style. cheers, felix
[Prev in Thread] | Current Thread | [Next in Thread] |