Hi, when I start gambit with:
/usr/local/Gambit-C/bin/gsi
things are fine, but if I start it with:
/usr/local/Gambit-C/bin/gsi -:s /usr/pkg/share/slib/gambit.init -
in order to get the slib stuff I have a problem with open-tcp-client
(open-tcp-client (list 'server-address: "zoo-crew.org" 'port-number: 80 'eol-encoding: 'cr-lf))
*** ERROR IN (console)@2.1 -- (Argument 1) Port settings expected (open-tcp-client '(server-address: "zoo-crew.org" port-number: 80 eol-encoding: cr-lf)) 1>
Is this a known problem? Is there a known fix? I'm using Gambit Version 4.0 beta 17
|/|/ Bendick
Afficher les réponses par date
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 17-Sep-06, at 2:29 AM, Will Bendick wrote:
Hi, when I start gambit with:
/usr/local/Gambit-C/bin/gsi
things are fine, but if I start it with:
/usr/local/Gambit-C/bin/gsi -:s /usr/pkg/share/slib/gambit.init -
in order to get the slib stuff I have a problem with open-tcp-client
(open-tcp-client (list 'server-address: "zoo-crew.org" 'port- number: 80 'eol-encoding: 'cr-lf))
*** ERROR IN (console)@2.1 -- (Argument 1) Port settings expected (open-tcp-client '(server-address: "zoo-crew.org" port-number: 80 eol-encoding: cr- lf)) 1>
Is this a known problem? Is there a known fix? I'm using Gambit Version 4.0 beta 17
The problem is the -:s option. This option places Gambit in "standard conformance" mode. In this mode server-address: is a *symbol*, not a keyword object. So the keyword parameter handler does not recognize this as a parameter keyword.
If you need to keep the -:s option, you can get around this problem with definitions like
(define server-address: (string->keyword "server-address")) (define port-number: (string->keyword "port-number")) ...
and create the open-tcp-client settings list without quotes on the keyword objects, i.e.
(open-tcp-client (list server-address: ...))
Marc
P.S. please use the Gambit bugzilla to post bugs: http:// www.iro.umontreal.ca/~gambit/bugzilla/