unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-user@gnu.org, guile-devel@gnu.org
Subject: Guile 1.6.7 has been released.
Date: Tue, 21 Dec 2004 12:26:10 -0600	[thread overview]
Message-ID: <87ekhjtsn1.fsf@trouble.defaultvalue.org> (raw)


We are pleased to announce the availability of a new Guile release.
This is the next maintenance release for the 1.6 stable series.

You can find it here:

  ftp://ftp.gnu.org/gnu/guile/guile-1.6.7.tar.gz.

Guile is Project GNU's extension language library, an interpreter for
Scheme, packaged as a library that you can link into your applications
to give them their own scripting language.  Guile should eventually
support other languages as well, giving users of Guile-based
applications a choice of languages.

This is primarily a bugfix release.  Highlights include:

  - A build problem has been fixed.  Previously, on some systems, the
    build would fail when libguile-ltdl couldn't be found during the
    build.

  - The array-map! and array-map-in-order! functions now allow a
    single source argument.  In prior versions, calls with just one
    source array were rejected.

  - A string->number overflow for bases other than 2, 10 and 16 has
    been fixed.  Among other things, this affected octal literal
    constants.

  - The argument order for the equality predicate passed to the SRFI-1
    functions alist-delete and alist-delete! now matches the SRFI-1
    specification.

  - In accordance with the SRFI-13 specification, the functions
    string-any and string-every now make a tail call to their
    predicate function upon reaching the last character in the string.

The Guile WWW page is located at

  http://www.gnu.org/software/guile/

It contains a link to the Guile FAQ and pointers to the mailing lists,
among other things.

Any bugs found in this release will be addressed by further bugfix
releases numbered 1.6.*.  The next stable Guile release with
significant functional improvements will be version 1.8.0.

In between 1.6.x and 1.8.x, you can follow Guile development in CVS
and in the Guile mailing lists (see ANON-CVS and HACKING).  Guile
builds from the development branch of CVS will have version number
1.7.0.

Guile versions with an odd middle number, i.e. 1.5.* are unstable
development versions.  Even middle numbers indicate stable versions.
This has been the case since the 1.3.* series.

Please send bug reports to bug-guile@gnu.org.

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592  F9A0 25C8 D377 8C7E 73A4


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


             reply	other threads:[~2004-12-21 18:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-21 18:26 Rob Browning [this message]
2004-12-22 18:41 ` Guile 1.6.7 has been released Neil Jerram
2004-12-22 20:14   ` Rob Browning
2004-12-23  1:20     ` Neil Jerram
2004-12-23  3:14       ` Rob Browning
2004-12-24 22:39         ` Neil Jerram
2004-12-25 22:37           ` Rob Browning

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ekhjtsn1.fsf@trouble.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=guile-devel@gnu.org \
    --cc=guile-user@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).