unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: rlb@defaultvalue.org, guile-devel@gnu.org, guile-user@gnu.org
Subject: Re: [d.love@dl.ac.uk: dynamic loading of native code modules]
Date: Sat, 20 Apr 2002 01:14:22 -0700	[thread overview]
Message-ID: <E16yq0k-0003ji-00@giblet> (raw)
In-Reply-To: <m3sn5vpf43.fsf@laruns.ossau.uklinux.net> (message from Neil Jerram on 16 Apr 2002 21:23:24 +0100)

   From: Neil Jerram <neil@ossau.uklinux.net>
   Date: 16 Apr 2002 21:23:24 +0100

   True, but I'm still slightly worried that one of the influences on
   {the set of people interested enough to maintain surrounding packages}
   might be a gradual trickle of incompatible changes in the core.

different users have different sensitivities to (interface) change.  for
some, any drop of incompatibility is like poison in the waterworks or
shameful rust buildup on an old tool, but others are not so allergic.
as a guile user, i tend to value the "hammer is clean and works the same
Always" approach (headbangers unite ;-).

   On the other hand, a project that doesn't change is a dead project,
   and packages that can't cope with a small amount of change may not be
   worth coddling, and I agree with you that the utility of recent
   additions and cleanups far exceeds that of Tcl/Tk and Ctax support.

it is useful to separate interface and implementation when discussion
change.  i would agree implementation change is inevitable and mostly
desirable, but not so easily taken wrt interface change.

guile users are all programmers who only marginally like hacking guile
itself.  interest can be motivated towards guile development by allowing
more guile users write privs, and practicing some mature process.

thi

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  parent reply	other threads:[~2002-04-20  8:14 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-12  1:06 [d.love@dl.ac.uk: dynamic loading of native code modules] Thien-Thi Nguyen
2002-04-13  8:50 ` Neil Jerram
2002-04-14  0:58   ` Rob Browning
2002-04-14 22:22     ` Neil Jerram
2002-04-15  4:21       ` Rob Browning
2002-04-16 20:23         ` Neil Jerram
2002-04-17  5:25           ` Rob Browning
2002-04-20  8:14           ` Thien-Thi Nguyen [this message]
2002-04-20 11:07             ` Neil Jerram
2002-04-15 12:15       ` Marius Vollmer
2002-04-16 20:24         ` Neil Jerram
2002-04-17  0:53           ` NIIBE Yutaka
2002-04-20  7:57             ` Thien-Thi Nguyen
2002-04-17  5:36           ` Rob Browning
2002-04-17  5:43             ` Rob Browning
2002-04-20  7:53             ` Thien-Thi Nguyen
2002-04-21 15:20               ` Rob Browning
2002-04-21 15:51                 ` Robert A. Uhl
2002-04-21 16:27                   ` Rob Browning
2002-05-14  8:53                 ` Thien-Thi Nguyen
2002-04-14 21:30   ` Marius Vollmer
2002-04-15 17:58     ` Andreas Rottmann
2002-04-15 19:06       ` Marius Vollmer
2002-04-24  8:00       ` Thien-Thi Nguyen
2002-04-24 14:33         ` Rob Browning
2002-04-24 14:51           ` rm
2002-04-24 15:14             ` Andreas Rottmann
2002-04-24 15:48               ` Rob Browning
2002-04-24 16:15                 ` Bill Gribble
2002-04-24 16:24                   ` Rob Browning
2002-04-24 18:10                   ` Andreas Rottmann
2002-04-24 20:36                     ` Rob Browning
     [not found]                     ` <87wuuwhm08.fsf@raven.i.defaultvalue.org>
2002-04-25  2:05                       ` Joshua Judson Rosen
2002-04-25  3:03                         ` Rob Browning
2002-04-24 18:06                 ` Andreas Rottmann
2002-04-24 20:40                   ` Rob Browning
2002-04-24 20:53                     ` Andreas Rottmann
2002-04-30  0:26                     ` Lynn Winebarger
2002-04-30  1:35                       ` Thien-Thi Nguyen
2002-04-30  2:33                         ` Lynn Winebarger
     [not found]                         ` <0204292133140I.10649@locke.free-expression.org>
2002-05-04  0:19                           ` Thien-Thi Nguyen
2002-04-30  0:20                 ` Lynn Winebarger
2002-04-24 15:28             ` Rob Browning
2002-05-15  0:19               ` Thien-Thi Nguyen
2002-04-24 18:34           ` Thien-Thi Nguyen
2002-04-24 18:58             ` Rob Browning
2002-04-25  5:32               ` Thien-Thi Nguyen
2002-05-01  5:00           ` Lynn Winebarger
2002-05-01 13:50             ` Rob Browning
2002-04-24  0:52     ` Thien-Thi Nguyen
2002-04-20  9:06   ` Thien-Thi Nguyen
2002-04-20 12:21     ` Neil Jerram
2002-04-20 12:44       ` Thien-Thi Nguyen
2002-04-24  0:09   ` Thien-Thi Nguyen
2002-04-14  0:34 ` Rob Browning
2002-04-14  2:55   ` Rob Browning
2002-04-24  0:24   ` Thien-Thi Nguyen
2002-04-24  5:25     ` Rob Browning
2002-04-24 21:18       ` Marius Vollmer
2002-04-25  4:10         ` Thien-Thi Nguyen
2002-04-28 15:32           ` Marius Vollmer
2002-04-28 20:19             ` Thien-Thi Nguyen
2002-05-14 10:57       ` Thien-Thi Nguyen
2002-05-14 16:11         ` Bill Gribble
2002-05-14 20:54           ` 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=E16yq0k-0003ji-00@giblet \
    --to=ttn@giblet.glug.org \
    --cc=guile-devel@gnu.org \
    --cc=guile-user@gnu.org \
    --cc=rlb@defaultvalue.org \
    --cc=ttn@glug.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).