unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-user@gnu.org
Subject: Re: The future: accessing vectors, arrays, etc from C
Date: Wed, 05 Jan 2005 00:04:28 +0000	[thread overview]
Message-ID: <41DB2F0C.9050304@ossau.uklinux.net> (raw)
In-Reply-To: <87acrvq1h5.fsf@zagadka.de>

Marius Vollmer wrote:
> Hi,
> 
> after some procrastination, I have more or less convinced myself to
> make accessing vectors and arrays (including uniform numeric vectors
> and arrays) more difficult from C.  Here is how and why.  Please
> comment!

Hi Marius,

Apologies for the slow response on this.  In general I think your 
proposal looks good, but I have two points to raise for consideration.

Firstly, I recall an old discussion between Jim and Mikael about a 
"leasing" interface in this area, which struck me at that time as very 
elegant.  I've not analysed how close it is to your thoughts, or how 
relevant it might be, but I thought you might like to review that and 
consider whether it affects your thinking at all.  The URLs of two 
relevant messages are:

http://sources.redhat.com/ml/guile/1999-01/msg00093.html
http://sources.redhat.com/ml/guile/1999-01/msg00109.html

Secondly, I am slightly concerned about the level of change that this 
means in the C API.  Actually, to be precise, I'm not sure I'm bothered 
about the level of change per se, as I believe the current reality is 
that a Guile application writer has no choice but to select an available 
major version of Guile (e.g. 1.6) and to target their application at 
specifically that version; and fortunately the bugs in Guile are few 
enough that it is feasible to stick with an older version.

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?

Regards,
	Neil


_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user


  parent reply	other threads:[~2005-01-05  0:04 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 [this message]
2005-01-05  4:12   ` Mike Gran
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=41DB2F0C.9050304@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --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).