[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Chicken-hackers] Ambiguity in csc's command line options (#1193)
From: |
Mario Domenech Goulart |
Subject: |
[Chicken-hackers] Ambiguity in csc's command line options (#1193) |
Date: |
Sat, 23 May 2015 22:33:20 +0000 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) |
Hi,
I've filed https://bugs.call-cc.org/ticket/1193 , which reports an isue
about ambiguity in csc's command line options.
Maybe CHICKEN 5 can be a good opportunity to fix that issue, since
backward compatibility is not such a big compromise,
Some options we have:
1. require a space between the parameter and the argument. So, `-lfoo'
would be an invalid option and `-l foo' would mean "link against
libfoo". -lfa2 would be a valid option, and would NOT mean "link
against libfa2".
2. support GNU-style command line options, that is, --<long> and -<l>.
Then we'd have --lfa2 to ask chicken to perform an additional
lightweight flow-analysis pass and -lfa2 to link against libfa2.
Any other ideas? Comments?
Best wishes.
Mario
--
http://parenteses.org/mario
- [Chicken-hackers] Ambiguity in csc's command line options (#1193),
Mario Domenech Goulart <=