> On May 13, 2015, at 11:55, Jim Ursetto wrote:
>
> #t does seem to make sense ... the existing behavior comes from the srfi-37
> implementation which sets the value to #f for #:none args. I could modify
> the args egg to change #f to #t in this case; I don't think this would cause
> any prob
On Wed, May 13, 2015 at 10:55 AM, Jim Ursetto wrote:
>
> #t does seem to make sense ... the existing behavior comes from the
> srfi-37 implementation which sets the value to #f for #:none args.
>
Oh, yes, I see. I think #f would be reasonable if you were processing
options with args-fold. Not so
On Wed, May 13, 2015 at 4:52 AM, Peter Bex wrote:
> On Wed, May 13, 2015 at 03:38:41AM -0600, Matt Gushee wrote:
> > Anyway, it seems that if you specify an option with no arguments, e.g.
> >
> >(args:make-option (v version) #:none
> > "Display compiled versions.
On Wed, May 13, 2015 at 03:38:41AM -0600, Matt Gushee wrote:
> Anyway, it seems that if you specify an option with no arguments, e.g.
>
>(args:make-option (v version) #:none
> "Display compiled versions.")
>
> ... then when the user invokes the program with that
Hello--
In the process of writing the command-line app that goes with the sass egg,
I noticed an issue with the args egg. I don't know if this is necessarily a
bug - maybe just an awkward feature.
Anyway, it seems that if you specify an option with no arguments, e.g.
(args:make-option (v vers
