unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Subject: Re: make-regexp error memory leak
Date: Sun, 11 Jul 2004 13:37:34 -0500	[thread overview]
Message-ID: <87ekniqtjl.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <878ydsk9qa.fsf@zip.com.au> (Kevin Ryde's message of "Sat, 10 Jul 2004 10:05:17 +1000")

Kevin Ryde <user42@zip.com.au> writes:

> Rob Browning <rlb@defaultvalue.org> writes:
>>
>> OK, once you get it working well, it should probably go into 1.6.
>
> Yep.  I made some changes.
>
> There's probably enough bits and pieces to have a release from the 1.6
> soon.  Especially since some of the fixes are actual wrong results for
> certain cases (logbit, round, ...).

Definitely.  There have been a lot of improvements.  I was waiting to
make sure we'd cleared up all the bugs on Marius' release-critical
list.  That's done now, so I'll be gearing up for a 1.6.5 release
soon.

However, I want to finish and commit my srfi-4 work first since it
fixes a number of bugs.  For example, try storing a large number in a
64-bit vector -- the printed representations are wrong.

-- 
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-07-11 18:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-04 23:51 make-regexp error memory leak Kevin Ryde
2004-07-07 17:41 ` Rob Browning
2004-07-08 23:57   ` Kevin Ryde
2004-07-09 18:03     ` Rob Browning
2004-07-10  0:05       ` Kevin Ryde
2004-07-11 18:37         ` Rob Browning [this message]
2004-07-23 23:06           ` Kevin Ryde
2004-07-27  1:56             ` 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=87ekniqtjl.fsf@trouble.defaultvalue.org \
    --to=rlb@defaultvalue.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).