From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Thien-Thi Nguyen Newsgroups: gmane.lisp.guile.user Subject: Re: 1.5.6: (bound? ) missing from optargs.scm Date: Thu, 28 Mar 2002 23:44:39 -0800 Sender: guile-user-admin@gnu.org Message-ID: References: Reply-To: ttn@glug.org NNTP-Posting-Host: localhost.gmane.org X-Trace: main.gmane.org 1017388139 27227 127.0.0.1 (29 Mar 2002 07:48:59 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Fri, 29 Mar 2002 07:48:59 +0000 (UTC) Cc: guile-user@gnu.org Original-Received: from fencepost.gnu.org ([199.232.76.164]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 16qr86-000751-00 for ; Fri, 29 Mar 2002 08:48:58 +0100 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16qr7F-0001Pl-00; Fri, 29 Mar 2002 02:48:05 -0500 Original-Received: from ca-crlsbd-u4-c4c-174.crlsca.adelphia.net ([68.66.186.174] helo=giblet) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16qr6R-0001KM-00 for ; Fri, 29 Mar 2002 02:47:15 -0500 Original-Received: from ttn by giblet with local (Exim 3.33 #1 (Debian)) id 16qr3v-0001eu-00; Thu, 28 Mar 2002 23:44:39 -0800 Original-To: tell@telltronics.org Errors-To: guile-user-admin@gnu.org X-BeenThere: guile-user@gnu.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: General Guile related discussions List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.lisp.guile.user:74 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.user:74 From: Steve Tell 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