From: Rob Browning <rlb@defaultvalue.org>
Cc: <guile-devel@gnu.org>, <guile-user@gnu.org>
Subject: Re: Roadmap and goals?
Date: Sat, 20 Apr 2002 15:01:33 -0500 [thread overview]
Message-ID: <871ydarvfm.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0204201305070.2654-100000@elm> (Kirill Lisovsky's message of "Sat, 20 Apr 2002 16:55:41 +0400 (MSD)")
Kirill Lisovsky <lisovsky@acm.org> writes:
> Guile - it is the slowest one, I'm afraid :-)
> Well, it's better _interpreter_ than Bigloo ...
> IMHO, it's main advantage is large installation/users base.
> But a mess with versions: 1.7.x , 1.6.x, 1.5.x while latest Linux distros
> are using 1.4.x or even 1.3.4!
> (1.3.4 is used by RedHat 7.2 which makes a lot of installed Guiles pretty
> obsolete...)
> Using Guile since 1999 I'm still ignoring its latest additions
> due to this zoo of versions...
After 1.3.4 it *should* be pretty clear -- the numbering scheme is the
same as that of the linux kernel now, given MAJOR.MINOR.MICRO,
releases with odd MINOR numbers are unstable, i.e. 1.5.* is an
unstable beta release, and even numbers are stable. 1.6.1 will be the
next stable release. Perhaps this isn't yet well enough known since
it was only decided after 1.4 and so is only documented in CVS ATM.
The problem with RedHat is a separate problem I think I understand
pretty well, and that I'm planning to try and help fix soon.
One issue in the FWIW category with respect to performance -- I've got
a partially working set of benchmarks here that I can run via a
"make". I'm planning to commit these tests to a CVS module (after I
make sure the copyrights allow that) so we can use it for checking our
work. Most of the benchmarks I have working right now are taken from
stalin, and so I've had to tone their workload down by orders of
magnitude so they'll actually run in a reasonable time with guile --
stalin is of course ridiculously faster in these tests.
> P.S. Forward of Nicolas's message to guile-user@gnu.org
> is the reason of this posting. Please, don't consider it as
> destructive :-)
Not at all, thanks for your comments.
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-04-20 20:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-20 12:55 Roadmap and goals? Kirill Lisovsky
2002-04-20 20:01 ` Rob Browning [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-17 12:21 Tanel Tammet
2002-04-17 20:59 ` Neil Jerram
2002-04-18 8:37 ` Panagiotis Vossos
2002-04-19 9:14 ` Panagiotis Vossos
2002-04-20 6:58 ` Thien-Thi Nguyen
2002-04-20 10:18 ` Panagiotis Vossos
2002-04-18 14:58 ` bitwize
2002-04-18 19:26 ` Rob Browning
2002-04-20 7:23 ` Thien-Thi Nguyen
2002-04-18 0:57 ` Christopher Cramer
2002-04-19 17:36 ` Marius Vollmer
2002-04-19 8:38 ` Nicolas Neuss
2002-04-21 15:14 ` Rob Browning
2002-04-21 22:26 ` bitwize
2002-04-22 18:36 ` Kirill Lisovsky
2002-04-23 7:53 ` rm
2002-04-23 15:11 ` Rob Browning
2002-04-20 7:47 ` Thien-Thi Nguyen
2002-05-14 8:26 ` Thien-Thi Nguyen
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=871ydarvfm.fsf@raven.i.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).