From: Mike Gran <spk121@yahoo.com>
Cc: guile-user@gnu.org
Subject: Re: The future: accessing vectors, arrays, etc from C
Date: Tue, 4 Jan 2005 20:12:20 -0800 (PST) [thread overview]
Message-ID: <20050105041220.21688.qmail@web14307.mail.yahoo.com> (raw)
In-Reply-To: <41DB2F0C.9050304@ossau.uklinux.net>
--- Neil Jerram <neil@ossau.uklinux.net> wrote:
> However, I wonder if perhaps we should have a more explicit and
> public
> policy on the level of change that is (i) acceptable and (ii) likely,
>
> from one major release to the next, so that developers know what to
> expect?
>
> What do you (and everyone else) think?
>
The design goals and expected improvements of 1.8 over 1.6 are unclear
to me. I don't track those discussions closely.
Every change to the API increases the risk of problems in updating a
code base, but, if the reward gained is great enough, the risk is
acceptable.
I'm fine with these array API changes. They work. If if should be
done, do it. But, it would be comforting to see that the API
approaches a frozen state as the design goals of 1.8 are met.
(If the API is sufficiently different to disallow interoperation
between a 1.6 codebase and a 1.8 codebase, it may as well be called
2.0.)
-
Mike Gran
__________________________________
Do you Yahoo!?
The all-new My Yahoo! - What will yours do?
http://my.yahoo.com
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2005-01-05 4:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 14:56 The future: accessing vectors, arrays, etc from C Marius Vollmer
2005-01-04 0:31 ` Kevin Ryde
2005-01-04 1:51 ` Marius Vollmer
2005-01-05 0:04 ` Neil Jerram
2005-01-05 4:12 ` Mike Gran [this message]
2005-01-05 18:10 ` Marius Vollmer
2005-01-05 11:52 ` Thien-Thi Nguyen
2005-01-05 18:01 ` Marius Vollmer
2005-01-06 19:13 ` Marius Vollmer
2005-01-06 23:08 ` Neil Jerram
2005-01-08 23:19 ` Neil Jerram
2005-01-11 18:01 ` Marius Vollmer
2005-01-11 19:53 ` Mikael Djurfeldt
2005-01-15 21:27 ` Neil Jerram
2005-01-16 8:06 ` Neil Jerram
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=20050105041220.21688.qmail@web14307.mail.yahoo.com \
--to=spk121@yahoo.com \
--cc=guile-user@gnu.org \
--cc=spikegran@earthlink.net \
/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).