guile 1.4.1.98 available

Thien-Thi Nguyen <[email protected]>
Newsgroups gmane.lisp.guile.user,gmane.lisp.guile.sources
Message-ID <[email protected]>
some bugfixes, some new stuff.  new NEWS excerpt below.  tarball in:

  http://www.glug.org/alt/

incidentally, the online manual, normally updated independently (and
more frequently), is at the moment sync'd w/ this release:

  http://www.glug.org/docbits/guile/1.4.x/

observant readers will notice a new chapter: Barely Explained Mysteries.

thi


_________________________________________________
* New module: (ice-9 md-data)

* Bugfix: (ice-9 q) proc `q-pop!'

* `while' macro

** Bugfix: `continue'

A bug was fixed within the body of a `while' macro, whereby a `continue'
expression would not properly avoid passing control flow to the expressions
following it.  For example, the following would display "bad":

  (let ((x 0))
    (while (< x 5)
      (if (= x 3)
          (begin
            (set! x 9)
            (continue)
            (write-line "bad")))
      (write-line x)
      (set! x (1+ x))))

** `break' argument now optional

Within a `while' macro, the `break' expression used to require an argument,
which would be used as the value for the `while'.  Now, specifying no argument
is also supported:

  (break)     => `while' value is #t
  (break VAL) => `while' value is VAL

* Bugfix: `accept' works with coop threads

It used to be that a call to `accept' in one thread would block all other
threads as well (presuming Guile is configured with `--enable-coop-threads').
The implementation now uses a thread-aware "internal `select'" on the socket's
associated file descriptor to arrange for the thread to yield if there is no
input pending.

* New procedure: (continuation? OBJ) => bool

[NEWS excerpt ends here]


_______________________________________________
Guile-user mailing list
[email protected]
http://mail.gnu.org/mailman/listinfo/guile-user
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.