chicken-users
[Top][All Lists]
Advanced

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

Re: [Chicken-users] CHICKEN 4.10.0 has been released


From: Claude Marinier
Subject: Re: [Chicken-users] CHICKEN 4.10.0 has been released
Date: Wed, 5 Aug 2015 16:46:17 -0400



On 4 August 2015 at 21:52, Peter Bex <address@hidden> wrote:
We are pleased to announce the immediate availability of CHICKEN 4.10.0
at the following URL:
http://code.call-cc.org/releases/4.10.0/chicken-4.10.0.tar.gz

Hi,

Had trouble with this release on MS Windows Vista (32-bit). Re-installed MinGW and tried again. Tried both from bash in MSYS and Windows' cmd. If works for a while before dying. Here is the relevant portion.

gcc -Wl,--enable-auto-import -shared -Wl,--out-implib,libchicken.dll.a \
          -o libchicken.dll library.o eval.o data-structures.o ports.o files.o extras.o lolevel.o utils.o tcp.o srfi-1.o srfi-4.o srfi-13.o srfi-14.o srfi-18.o srfi-69.o posixwin.o irregex.o scheduler.o profiler.o stub.o expand.o modules.o chicken-syntax.o chicken-ffi-syntax.o build-version.o runtime.o apply-hack.x86.o -lm -lws2_32
library.o:library.c:(.text+0x342b8): undefined reference to `getc_unlocked'
library.o:library.c:(.text+0x34310): undefined reference to `getc_unlocked'
library.o:library.c:(.text+0x3433e): undefined reference to `getc_unlocked'
c:/mingw/bin/../lib/gcc/mingw32/4.8.1/../../../../mingw32/bin/ld.exe: library.o: badreloc
 address 0x0 in section `.data'
collect2.exe: error: ld returned 1 exit status
make: *** [libchicken.dll] Error 1

Complete output available if needed.

Thanks.
 
This tarball has the following SHA256 checksum:
0e07f5abcd11961986950dbeaa5a40db415f8a1b65daff9c300e9b05b334899b

This is mostly a bugfix release, containing quite a lot of accumulated
bug fixes but relatively few new features.  Nevertheless, there are a
great many changes in this release since 4.9.0.  It has three security
bugfixes: for CVE-2014-6310, CVE-2014-9651 and CVE-2015-4556.

Another important security-related cleanup/improvement is related to path
expansion: many file procedures in CHICKEN used to automatically and
implicitly convert paths containing tilde ("~") characters to $HOME,
and expand shell variables.  This behaviour was deprecated in 4.9.0,
and has now been removed, in favor of the "pathname-expand" egg.

A few of the build variables have been renamed, so if you have a custom
build script, please review the NEWS file carefully.

Other notable changes:

* The performance of reading and writing SRFI-4 u8vectors has been
   substantially improved.
* Various bugs in the functors implementation have been fixed, making
   them better usable.
* chicken.h can once more be correctly compiled with a C++ compiler.
* The -r5rs-syntax flag has been fixed to enforce r5rs syntax.

For the full list of changes, see
http://code.call-cc.org/releases/4.10.0/NEWS-4.10.0

Many thanks to all of you who have helped to test the release candidates,
provided bug reports, feedback and improvements.

Kind regards,
The CHICKEN Team
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: Digital signature
URL: <http://lists.nongnu.org/archive/html/chicken-users/attachments/20150804/b3530e99/attachment.pgp>

------------------------------

Message: 3
Date: Wed, 5 Aug 2015 09:09:57 +0200
From: Christian Kellermann <address@hidden>
To: address@hidden
Cc: address@hidden
Subject: [Chicken-users] [ICC 2015] Reminder for T-Shirts
Message-ID: <address@hidden>
Content-Type: text/plain; charset=us-ascii

Hello!

As I have written before I will be organising another round of CHICKEN
T-Shirt prints. To put that plan into action I need a rough idea on
how many shirts should be made and of course which size will fit you!

So this is your friendly reminder that you need to tell me your shirt
sizes! The laudable andyjpb has been the first and only responder so
far on the wiki page. If your shirt size is a secret please mail me
the wanted size and quantity. The final prize for each shirt depends
on the overall amount.

So there will be a deadline for orders and it's August 18th midnight UTC.

So get up, rip your shirt off and look at the label in the back, maybe
adjust the size and tell me!

The place in the wiki is the shirts section on
http://wiki.call-cc.org/event/intercontinental-chicken-conference-2015

Kind regards,

Christian

P.S.: You may put your shirts back on now, thanks.

--
May you be peaceful, may you live in safety, may you be free from
suffering, and may you live with ease.



------------------------------

Message: 4
Date: Wed, 05 Aug 2015 10:11:15 -0400
From: Nick Andryshak <address@hidden>
To: address@hidden
Subject: [Chicken-users] What use, if any, is `any?' ?
Message-ID: <address@hidden>
Content-Type: text/plain

Hello!

I came across this function in the official documentation recently:

http://wiki.call-cc.org/man/4/Unit%20data-structures#any

>any?
>[procedure] (any? X)
>Ignores its argument and always returns #t. This is actually useful
>sometimes.

Is it, though? Does anyone have any practical examples? And why couldn't
you just replace any usages of (any? x) with just plain #t?

Thanks,

Nick



------------------------------

Message: 5
Date: Wed, 05 Aug 2015 15:00:28 +0000
From: Mario Domenech Goulart <address@hidden>
To: address@hidden
Subject: Re: [Chicken-users] What use, if any, is `any?' ?
Message-ID: <address@hidden>
Content-Type: text/plain

Hi Nick,

On Wed, 05 Aug 2015 10:11:15 -0400 Nick Andryshak <address@hidden> wrote:

> I came across this function in the official documentation recently:
>
> http://wiki.call-cc.org/man/4/Unit%20data-structures#any
>
>>any?
>>[procedure] (any? X)
>>Ignores its argument and always returns #t. This is actually useful
>>sometimes.
>
> Is it, though? Does anyone have any practical examples? And why couldn't
> you just replace any usages of (any? x) with just plain #t?

Combinators are usually useful when used as arguments to procedures.

Not really a practical example, but just to illustrate a case with any?:

  (define (foo proc)
    (proc 42))

  (print (foo negative?))
  (print (foo any?))

You can't really use (foo #t), since foo expects a procedure as
argument.  You may argue that you could simply use (print #t), but then
you don't need a combinator in the first place. :-)

Best wishes.
Mario
--
http://parenteses.org/mario



------------------------------

Message: 6
Date: Wed, 5 Aug 2015 17:10:04 +0200
From: Pierpaolo Bernardi <address@hidden>
To: Nick Andryshak <address@hidden>
Cc: chicken <address@hidden>
Subject: Re: [Chicken-users] What use, if any, is `any?' ?
Message-ID:
        <address@hidden>
Content-Type: text/plain; charset=UTF-8

On Wed, Aug 5, 2015 at 4:11 PM, Nick Andryshak <address@hidden> wrote:
> Hello!
>
> I came across this function in the official documentation recently:
>
> http://wiki.call-cc.org/man/4/Unit%20data-structures#any
>
>>any?
>>[procedure] (any? X)
>>Ignores its argument and always returns #t. This is actually useful
>>sometimes.
>
> Is it, though? Does anyone have any practical examples? And why couldn't
> you just replace any usages of (any? x) with just plain #t?

You can indeed replace (any? x) with plain #t when any? is present in
literal form in a call, but functions are first class objects and can
be passed around.

Suppose you have a function which searches for foos which satisfy a
predicate in a container, like:

(search-foo container predicate)

If any foo will do for you, you can use it as (search-foo container any?)

During the evaluation of this call to search-foo there will be a
function application that in this particular call will be an
application of the any? function, and that comes handy, sometimes.

P.



------------------------------

_______________________________________________
Chicken-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/chicken-users


End of Chicken-users Digest, Vol 153, Issue 3
*********************************************



--
Claude Marinier

reply via email to

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