chicken-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Chicken-hackers] [PATCH] Fix bad call in chicken-install error situatio


From: Peter Bex
Subject: [Chicken-hackers] [PATCH] Fix bad call in chicken-install error situation
Date: Thu, 12 Jul 2012 20:46:47 +0200
User-agent: Mutt/1.4.2.3i

Hi all,

I had some networking trouble just now and noticed that chicken-install
showed the following output, which is obviously incorrect:

TCP connect timeout

Error: bad argument count - received 2 but expected 3: #<procedure>

A similar situation can easily be triggered by calling chicken-install
with a nonexistent hostname:

$ chicken-install -l foo bar
retrieving ...
connecting to host "foo", port 80 ...
TCP connect timeout

Error: bad argument count - received 2 but expected 3: #<procedure>

The attached patch fixes the immediate error by calling "proc" with
three arguments instead of two.  However, I'm still a little unsure
how this is supposed to work.  For example, in
list-available-extensions, if "trans" is false, it will invoke the
NEXT procedure, which is #f.  I've tried but was unable to trigger
an error situation, so I suppose it's okay the way it is (but I still
don't understand).

Cheers,
Peter
-- 
http://sjamaan.ath.cx
--
"The process of preparing programs for a digital computer
 is especially attractive, not only because it can be economically
 and scientifically rewarding, but also because it can be an aesthetic
 experience much like composing poetry or music."
                                                        -- Donald Knuth

Attachment: 0001-Also-call-proc-with-three-arguments-in-with-default-.patch
Description: Text document


reply via email to

[Prev in Thread] Current Thread [Next in Thread]