Alright, one more email for tonight. I have noticed lately (don't know when
it started, but I suppose at least since I started using Chicken 4.9.0.1),
that every time I compile anything with csc, I get this warning:
In file included from /usr/include/ctype.h:25:0,
from
Hello, chickeneers--
I am proud to announce the first release of the sass egg. This is a wrapper
for libsass [http://libsass.org], which is the C/C++ library version of the
Sass CSS preprocessor.
At present, this egg is very low-level - it's mostly just a straight
translation of the C API into
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
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 option,
Hi Matt,
This has been addressed in the development tree and the warnings will go
away with the next release.
As for hiding the warnings on 4.9.0.1, you could try passing a flag to
silence them as a C compiler option (perhaps -Wno-deprecated? I don't
know which option will suppress these
Hi, Evan--
On Wed, May 13, 2015 at 6:54 PM, Evan Hanson ev...@foldling.org wrote:
$ csc -C -D_DEFAULT_SOURCE foo.scm
Oh, yeah. Duh. Why, I bet I could even add it to my bash profile, since it
is pretty unlikely I'll be working on any projects where I need to see that
warning.
Thanks,
On May 13, 2015, at 11:55, Jim Ursetto zbignie...@gmail.com 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
Hi, Moritz--
On Thu, Apr 16, 2015 at 2:35 PM, Moritz Heidkamp mor...@twoticketsplease.de
wrote:
sorry for the late reply, got busy :-)
And I'm sorry for the even later reply, got scared :-)
No, really! It's stupid, but I am often scared of people's reactions when I
make even mildly critical
On Wed, May 13, 2015 at 10:55 AM, Jim Ursetto zbignie...@gmail.com 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
On Wed, May 13, 2015 at 4:52 AM, Peter Bex pe...@more-magic.net 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
10 matches
Mail list logo
