From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: guile-user@gnu.org
Subject: Re: 1.5.6: (bound? ) missing from optargs.scm
Date: Thu, 28 Mar 2002 23:44:39 -0800 [thread overview]
Message-ID: <E16qr3v-0001eu-00@giblet> (raw)
In-Reply-To: Pine.LNX.4.21.0203290059400.11739-100000@ariel.lan.telltronics.org
From: Steve Tell <tell@telltronics.org>
Date: Fri, 29 Mar 2002 01:40:57 -0500 (EST)
[removing bound? makes lambda*/define* less useful]
this change breaks code that relies on def/undef as "valid bit".
programs that model and/or use such communication channels (e.g.,
hardware simulators) now need to implement that protocol. if the
program already uses #f (the "obvious logical" fix) now it needs to
additionally define "my-undef". otherwise it can use #f.
THUD author seethes inside (wtf! what a PITA), but i think i can see how
this change supports encapsulation, and so "re-layering" of the API
using some other out-of-band object is possible. (we can bring `bound?'
back. we just need to finish this iso-API change in the right way, or
justify in NEWS the new API.)
wrt other woes, when i took guile-snarf off of noinst_ i did not take
advantage of the dist-hook to modify already-distributed guile-snarf to
emit warnings when run, even though i thought about it. my bad.
the story is that what we discussed and i implemented, mvo munged so
that SCM_MAGIC_SNARFER is now exposed/required/forgotten/fubared and
documented. from no design to bad design, IMO.
Anyway, I am now successfuly building on 1.4 and 1.5.6, with 1.3.4
testing still remaining. I feel like I have to support 1.3.4 until
more of the major linux distributions start shipping with 1.4 or
later.
some upgrade policies have proven difficult to foresee by guile
maintainers. maybe someone will fork guile and merge it w/ chicken.
(this is how you trick distributors into upgrading. ;-)
actually, this reminds me i need to get 1.4.1 out.
thi
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2002-03-29 7:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-28 6:30 1.5.6: (bound? ) missing from optargs.scm Steve Tell
2002-03-28 8:52 ` Thien-Thi Nguyen
2002-03-28 23:32 ` Thien-Thi Nguyen
2002-03-29 6:40 ` Steve Tell
2002-03-29 7:44 ` Thien-Thi Nguyen [this message]
2002-03-30 2:26 ` Steve Tell
2002-03-30 4:42 ` Thien-Thi Nguyen
2002-03-31 22:06 ` Marius Vollmer
2002-04-01 1:42 ` Thien-Thi Nguyen
2002-03-31 22:46 ` Marius Vollmer
2002-04-24 17:52 ` Marius Vollmer
2002-03-31 22:59 ` 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=E16qr3v-0001eu-00@giblet \
--to=ttn@giblet.glug.org \
--cc=guile-user@gnu.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).