headers
matt welland | 1 Feb 2011 06:28
Favicon

Announce: chicken-iup installer 0.2 available

This version integrates chicken 4.6.3, and the iup and data draw eggs into a single exe installer for windows.

I have added a link on the call-cc.org binary downloads page to my fossil page here: http://www.kiatoa.com/cgi-bin/chicken-iup

There are a couple of sample scripts in the c:/chicken/examples directory but note that they need to be re-written to be more schemish.


_______________________________________________
Chicken-users mailing list
Chicken-users <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users
Permalink | Reply | 0 comments |
headers
pmarin | 1 Feb 2011 12:00
Picon
Gravatar

How can I get an offline version of the manual

Is there any way to get an offline version of the manual?
I know that the source is in ./manual but I don't know how can i build
it. Is there any 'make' option for that?

Cheers.
pmarin
Permalink | Reply | 3 comments |
headers
Peter Bex | 1 Feb 2011 13:14
Picon
Picon
Favicon

Re: http-client doesn't handle closed persistent connections

On Tue, Feb 01, 2011 at 06:58:23AM +0900, Daishi Kato wrote:
> Tried the trunk, working fine.
> I don't see any problems now.
> Thank you!

Thank you for reporting this and the fine testcase!

I've now tagged a new 0.4.1 release with this bugfix.

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
Permalink | Reply | 0 comments |
headers
Thomas Hintz | 2 Feb 2011 02:03

SRFI-19 Error

Using csi and GNU readline (I don't think I'm doing anything wrong...):


#> (use srfi-19)
#> (date-subtract-duration (current-date) (make-duration days: 3))

Error: (+) bad argument type - not a number: #<input port "(gnu-readline)">

        Call history:

        def-tt304312      
        srfi-19-date#default-date-clock-type      
        body302308        
        srfi-19-support#tm:date->time     
        srfi-19-support#tm:as-some-time   
        srfi-19-support#tm:subtract-duration      
        srfi-19-support#tm:date-timezone-info     
        srfi-19-date#tm:time->date/tzi    
        srfi-19-support#tm:time->date     
        locale-components#locale-components?

Another error:

#> (date-add-duration (current-date) (make-duration days: 3))
#,(date 318000000 24 3 7 31 8 2020 -18000 EST #f #f #f #f)

This is not the correct date...

It doesn't seem to matter if I use make-date or current-date. current-date is:

#> (current-date)
#,(date -778000000 55 0 20 1 2 2011 -18000 EST #f #f #f #f)

This is on Chicken 4.6.3 on Arch Linux i686.

If I'm doing something wrong, please let me know, otherwise I would be glad to help pin-point the bug.

Thanks,

Thomas Hintz
_______________________________________________
Chicken-users mailing list
Chicken-users <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users
Permalink | Reply | 1 comment |
headers
Kon Lovett | 2 Feb 2011 02:19
Picon
Gravatar

Re: SRFI-19 Error

Hello Thomas,

This is a bug. I will look into it. Sorry but thank you for reporting.

Kon

On Feb 1, 2011, at 5:03 PM, Thomas Hintz wrote:

> Using csi and GNU readline (I don't think I'm doing anything  
> wrong...):
>
> #> (use srfi-19)
> #> (date-subtract-duration (current-date) (make-duration days: 3))
>
> Error: (+) bad argument type - not a number: #<input port "(gnu- 
> readline)">
>
>         Call history:
>
>         def-tt304312
>         srfi-19-date#default-date-clock-type
>         body302308
>         srfi-19-support#tm:date->time
>         srfi-19-support#tm:as-some-time
>         srfi-19-support#tm:subtract-duration
>         srfi-19-support#tm:date-timezone-info
>         srfi-19-date#tm:time->date/tzi
>         srfi-19-support#tm:time->date
>         locale-components#locale-components?
>
> Another error:
>
> #> (date-add-duration (current-date) (make-duration days: 3))
> #,(date 318000000 24 3 7 31 8 2020 -18000 EST #f #f #f #f)
>
> This is not the correct date...
>
> It doesn't seem to matter if I use make-date or current-date.  
> current-date is:
>
> #> (current-date)
> #,(date -778000000 55 0 20 1 2 2011 -18000 EST #f #f #f #f)
>
> This is on Chicken 4.6.3 on Arch Linux i686.
>
> If I'm doing something wrong, please let me know, otherwise I would  
> be glad to help pin-point the bug.
>
> Thanks,
>
> Thomas Hintz
> _______________________________________________
> Chicken-users mailing list
> Chicken-users <at> nongnu.org
> http://lists.nongnu.org/mailman/listinfo/chicken-users
Permalink | Reply | 0 comments |
headers
schugk | 2 Feb 2011 15:42
Picon
Favicon

Re: coops

> So you example above should basically work, but note that the method
> for `<pair>' will always override the one for `<list>', since the
> latter is a supertype of the former.

That is the problem i am talking about. I know the reason. The new  
version (1.4) does not fix that. I can not call a specialized method  
for <list> if it is specialized for <pair> too. One solution is to  
specialize show for <list> after that one for <pair>. That is not  
possible if <pair> should inherit from <list>. ... Ok, i have to  
change that in my local version of coops and mention it in the  
documentation.

Sandro
Permalink | Reply | 0 comments |
headers
schugk | 2 Feb 2011 18:24
Picon
Favicon

Re: coops

Sometimes the simplest solution are the hardest to see. I do not have  
to use coops-primitive-objects, I can define my own hierarchie of  
primitive objects.

Sandro
Permalink | Reply | 4 comments |
headers
Stephen Eilert | 2 Feb 2011 19:32
Picon
Gravatar

Re: coops

On Wed, Feb 2, 2011 at 2:24 PM,  <schugk <at> uni-potsdam.de> wrote:
> Sometimes the simplest solution are the hardest to see. I do not have to use
> coops-primitive-objects, I can define my own hierarchie of primitive
> objects.

That is my experience as well. Every time I import
coops-primitive-objects, I end up removing it some time later.

--Stephen

Sent from my Emacs
Permalink | Reply | 3 comments |
headers
Felix | 2 Feb 2011 21:29

Re: coops

From: Stephen Eilert <spedrosa <at> gmail.com>
Subject: Re: [Chicken-users] coops
Date: Wed, 2 Feb 2011 15:32:33 -0300

> On Wed, Feb 2, 2011 at 2:24 PM,  <schugk <at> uni-potsdam.de> wrote:
>> Sometimes the simplest solution are the hardest to see. I do not have to use
>> coops-primitive-objects, I can define my own hierarchie of primitive
>> objects.
> 
> That is my experience as well. Every time I import
> coops-primitive-objects, I end up removing it some time later.

After all the work I put into it? My heart bleeds ...

cheers,
felix
Permalink | Reply | 2 comments |
headers
Stephen Eilert | 2 Feb 2011 22:50
Picon
Gravatar

Re: coops

On Wed, Feb 2, 2011 at 5:29 PM, Felix
<felix <at> call-with-current-continuation.org> wrote:
> From: Stephen Eilert <spedrosa <at> gmail.com>
> Subject: Re: [Chicken-users] coops
> Date: Wed, 2 Feb 2011 15:32:33 -0300
>
>> On Wed, Feb 2, 2011 at 2:24 PM,  <schugk <at> uni-potsdam.de> wrote:
>>> Sometimes the simplest solution are the hardest to see. I do not have to use
>>> coops-primitive-objects, I can define my own hierarchie of primitive
>>> objects.
>>
>> That is my experience as well. Every time I import
>> coops-primitive-objects, I end up removing it some time later.
>
> After all the work I put into it? My heart bleeds ...

I've yet to define generic methods on, say, continuations or threads.
I assume coops-primitive-objects will be much more useful for those.
The issue is not with coops-primitive-objects. Instead, as a program
progresses it is sometimes useful to redefine old functions and have
them accept more 'specialized' objects.

Maybe that's just me.

--Stephen

Sent from my Emacs
Permalink | Reply | 1 comment |

Gmane