Re: [Chicken-users] riaxpander bug(?) with #!optional
On Wed, Jun 18, 2008 at 2:45 AM, Peter Wright <[EMAIL PROTECTED]> wrote: > > It _looks_ like this is the failing line from riaxpander: > > http://trac.callcc.org/browser/release/3/riaxpander/riaxpander-chicken-macros.scm?rev=10322#L248 > > ...but I'm not sure what it's supposed to be doing. And the > indentation looks wrong (which tends to be a good hint of badness in > my *own* code at least :)). > > Ah well, I'll investigate it a bit further and perhaps compare with > the syntactic-closures implementation. > Sorry, I haven't got a clue. Perhaps Alex Shinn can say something about this. Or better Taylor Campbell, the original author. cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Soundex
On 6/16/08, Kyle R. Burton <[EMAIL PROTECTED]> wrote: >> [felix wrote] >> Well, why don't you make eggs from the stuff? I'd be delighted >> to add it to the repository and can give you commit rights, if >> you like. > I'd be delighted to. If we want that to happen sooner rather than > later, I'll request some hand holding. If you can wait on my free > time (er, uh) then it'll take significantly longer. The hand holding > could be as simple as: go here, read this, do these steps, email the > list w/questions. See the tutorial at http://chicken.wiki.br/eggs%20tutorial . Basically, check out a read-write copy of the repository using your (forthcoming) SVN userid, and study that wiki page and the existing eggs. Looking at existing eggs really helps when learning to do things The Chicken Way. You can study existing eggs and create your own eggs locally without read-write access in the meantime. ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] tcp-read-timeout: procedure or parameter?
The wiki says it's a parameter: , | http://chicken.wiki.br/Unit%20tcp#tcp-read-timeout | | tcp-read-timeout | | [parameter] tcp-read-timeout | | Determines the timeout for TCP read operations in milliseconds. A | timeout of #f disables timeout checking. The default read timeout is | 6, i.e. 1 minute. ` In csi, it's actually a procedure: , | #;1> (use tcp) | ; loading library tcp ... | #;2> tcp-read-timeout | # | #;3> ` So what's the correct way of disabling read timeout? Like this? , | (define (tcp-read-timeout) #f) ` What I'm trying to do is, in a tcp connection: I'd like to pass some socket options like keep-alive, so as to make the client says connected. Any ideas? ,[ version ] | Version 3.2.5 - macosx-unix-gnu-x86-64[ 64bit manyargs dload ptables applyhook ] ` -- William http://williamxu.net9.org neutron bomb, n.: An explosive device of limited military value because, as it only destroys people without destroying property, it must be used in conjunction with bombs that destroy property. ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] Chicken pre-release 3.3.0
Hi all, I have merged the Chicken trunk with the prerelease branch in the SVN repository, and I plan on making another minor release of Chicken before the end of the month. This will include bug fixes that have accumulated over the past two months, as well as new unit ports factored out from unit extras. I have run salmonella under Linux with this prerelease, and I will do another run under MacOS X. Please try it out and let me know if there are any problems. -Ivan -- "Their eyes met, and his heart soared, like the price of gas before a long weekend." --Cornered, by Mike Baldwin ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] tcp-read-timeout: procedure or parameter?
On Tue, Jun 24, 2008 at 7:44 AM, William Xu <[EMAIL PROTECTED]> wrote: > The wiki says it's a parameter: > > , > | http://chicken.wiki.br/Unit%20tcp#tcp-read-timeout > | > | tcp-read-timeout > | > | [parameter] tcp-read-timeout > | > | Determines the timeout for TCP read operations in milliseconds. A > | timeout of #f disables timeout checking. The default read timeout is > | 6, i.e. 1 minute. > ` > > In csi, it's actually a procedure: > > , > | #;1> (use tcp) > | ; loading library tcp ... > | #;2> tcp-read-timeout > | # > | #;3> > ` > > So what's the correct way of disabling read timeout? Like this? > A parameter is a special kind of procedure. You access it like this: (tcp-read-timeout) -> (tcp-read-timeout ) > > What I'm trying to do is, in a tcp connection: I'd like to pass some > socket options like keep-alive, so as to make the client says connected. > Any ideas? There is now API for that, yet. But see the function ##sys#bind-socket in tcp.scm for an example of the use of socket options. I guess we have to add support for this. cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] tcp-read-timeout: procedure or parameter?
On Tue, Jun 24, 2008 at 8:26 AM, felix winkelmann <[EMAIL PROTECTED]> wrote: > > There is now API for that, yet. But see the function ##sys#bind-socket in > tcp.scm for an example of the use of socket options. I guess we have to > add support for this. > Sorry, it's "##net#bind-socket". cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
