From: Roland Orre <orre@nada.kth.se>
Cc: guile-user@gnu.org
Subject: Re: Worrying development
Date: Fri, 16 Jan 2004 12:34:25 +0100 [thread overview]
Message-ID: <1074252865.6739.77.camel@localhost> (raw)
In-Reply-To: <E1AhS17-0008BT-00@surf.glug.org>
On Fri, 2004-01-16 at 12:19, Thien-Thi Nguyen wrote:
> From: Roland Orre <orre@nada.kth.se>
> Date: Fri, 16 Jan 2004 10:41:05 +0100
>
> to be able to utilize facilities which are only available there.
>
> which facilities are these? (could you be more specific?)
The statement was not very specific and what I was thinking about was
not very specific, more based upon the general expectation that a new
version contains new functions (usually... now it was the opposite).
The main reason, however, for me to continue with 1.7 after 1.6 is that
as I've understood from Mikael Djurfeldt goops and the corresponding
matrix handling are only fully supported in 1.7. There is also real
pthreads support, which I've however not utilized yet, this is more
like a nice future potential. The only thing which I'll be dependent
on is goops support.
Another nice thing with guile 1.7, as I've understood, is that the
garbage collector now is utilizing Robert Strand's (Bobby Beach)
old idea to have the garbage collection bits separated from the
actual tags. This gives potentials for e.g. background garbage
collection as a parallell process. (I was by the way working with
Robert Strand at ASEA in the beginning of the 80ies when he invented
this idea).
Of course we also have the GMP support in 1.7, even though this is
nice, I won't use it myself very much. Mostly I'm doing number
crunching, statistical analysis and data base handling.
Best regards
Roland
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2004-01-16 11:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 9:41 Worrying development Roland Orre
2004-01-16 11:19 ` Thien-Thi Nguyen
2004-01-16 11:34 ` Roland Orre [this message]
2004-01-24 22:44 ` Thien-Thi Nguyen
2004-01-16 11:59 ` tomas
2004-01-18 21:05 ` Marius Vollmer
2004-01-18 21:58 ` Tom Lord
2004-01-22 16:11 ` Dirk Herrmann
2004-01-22 18:26 ` Shared Substrings [was: Worrying development] Robert Uhl
2004-01-22 18:42 ` Worrying development Tom Lord
2004-01-23 11:45 ` Dirk Herrmann
2004-01-23 17:16 ` Tom Lord
2004-01-23 21:01 ` Marius Vollmer
2004-01-23 22:18 ` Tom Lord
2004-01-24 0:27 ` Marius Vollmer
2004-01-24 0:53 ` Tom Lord
2004-01-23 22:28 ` Paul Jarc
2004-01-24 12:09 ` rm
2004-01-24 13:29 ` Marius Vollmer
2004-01-26 2:42 ` overriding car/cdr (was: Worrying development) Paul Jarc
2004-02-08 16:21 ` overriding car/cdr Dirk Herrmann
2004-02-08 18:09 ` Marius Vollmer
2004-02-08 20:56 ` Paul Jarc
2004-03-20 22:28 ` Marius Vollmer
2004-03-22 17:05 ` David Van Horn
2004-03-22 21:03 ` Marius Vollmer
2004-03-22 17:24 ` Paul Jarc
2004-01-23 22:37 ` Worrying development Dirk Herrmann
2004-01-23 23:25 ` Tom Lord
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=1074252865.6739.77.camel@localhost \
--to=orre@nada.kth.se \
--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).