From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: neil@ossau.uklinux.net, guile-devel@gnu.org
Subject: Re: Remove objprop.c from libguile?
Date: Wed, 03 Apr 2002 00:09:46 -0800 [thread overview]
Message-ID: <E16sfpx-0002Zi-00@giblet> (raw)
In-Reply-To: <87n0x2yjun.fsf@zagadka.ping.de> (message from Marius Vollmer on 20 Mar 2002 23:06:56 +0100)
From: Marius Vollmer <mvo@zagadka.ping.de>
Date: 20 Mar 2002 23:06:56 +0100
> Instead, we should probably deprecate (in 1.8) the whole of objprop.c
> in its current form, and remove it in 1.10.
Even better!
and best if some kind of statement can be recorded on when (and why)
deprecation of this is to result in removal. version name can be used
if a version is completely specified (at its interface), a concurrent
task unlikely to be fulfilled until the moment of release (so sez hw
dudes).
it behooves us to define 1.6+ feature sets (lists of positive attributes
(rather than negative attributes like "no longer has objprop.c")), so
that when we say "1.10 for removal" it is possible to correlate further
up the chain to "make things better", e.g.:
- make things better
- provide unified property management ;; also a "feature"
- simplify API
- add new stuff
- remove old stuff ;; bye bye objprop.c
- 1.10
- features
- unified property management
- bye-bye
- objprop.c -- 1.10
if we don't record these things more formally than m.l. traffic, some
tool will have to dig archives later, led around by a human (blech).
thi
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-04-03 8:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 13:52 Remove objprop.c from libguile? Neil Jerram
2002-03-15 21:32 ` Marius Vollmer
2002-03-17 14:49 ` Neil Jerram
2002-03-20 22:06 ` Marius Vollmer
2002-04-03 8:09 ` Thien-Thi Nguyen [this message]
2002-03-15 21:35 ` Marius Vollmer
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=E16sfpx-0002Zi-00@giblet \
--to=ttn@giblet.glug.org \
--cc=guile-devel@gnu.org \
--cc=neil@ossau.uklinux.net \
--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).