From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Thien-Thi Nguyen Newsgroups: gmane.lisp.guile.devel Subject: Re: git push weird? Date: Tue, 15 Jun 2010 23:56:28 +0200 Message-ID: <87wru0m037.fsf@ambire.localdomain> References: <87fx0ozfx1.fsf@ambire.localdomain> <87sk4onmzw.fsf@gnu.org> <871vc8nl0g.fsf@ambire.localdomain> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1276640194 10669 80.91.229.12 (15 Jun 2010 22:16:34 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 15 Jun 2010 22:16:34 +0000 (UTC) Cc: Ludovic =?utf-8?Q?Court=C3=A8s?= , guile-devel@gnu.org To: Andy Wingo Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Wed Jun 16 00:16:33 2010 connect(): No such file or directory Return-path: Envelope-to: guile-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1OOeQn-0007Fm-UA for guile-devel@m.gmane.org; Wed, 16 Jun 2010 00:16:30 +0200 Original-Received: from localhost ([127.0.0.1]:45203 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OOeNb-0004Ip-Vg for guile-devel@m.gmane.org; Tue, 15 Jun 2010 18:13:12 -0400 Original-Received: from [140.186.70.92] (port=35715 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OOeMx-0003rj-Lt for guile-devel@gnu.org; Tue, 15 Jun 2010 18:12:34 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OOeFd-0001mE-8D for guile-devel@gnu.org; Tue, 15 Jun 2010 18:04:58 -0400 Original-Received: from smtp204.alice.it ([82.57.200.100]:36230) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OOe9p-000147-FP; Tue, 15 Jun 2010 17:58:57 -0400 Original-Received: from ambire.localdomain (95.244.64.180) by smtp204.alice.it (8.5.124.05) id 4C0E61C00076B551; Tue, 15 Jun 2010 23:58:43 +0200 Original-Received: from ttn by ambire.localdomain with local (Exim 4.69) (envelope-from ) id 1OOe7Q-000222-41; Tue, 15 Jun 2010 23:56:28 +0200 In-Reply-To: (Andy Wingo's message of "Tue, 15 Jun 2010 23:07:47 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.devel:10493 Archived-At: () Andy Wingo () Tue, 15 Jun 2010 23:07:47 +0200 Just for readability I have rebased the commits. The gnulib commit will get overwritten at the next gnulib import. GUILE_CONFIG_SCRIPT is fine. OK, thanks for cleaning up my mess. It's good to have tmpfile, but I wonder about making the port-filename not a string or #f. 'tmpfile seems too magical to me; if you're working from scheme you can always associate a tmpfile object property on the port, and I wouldn't want people to start asking if it's a tmpfile. So I have changed it to return #f. Why wouldn't you want people to start asking if it's a tmpfile? People are curious. If you really think that 'tmpfile is the right thing, let's talk about it :) One way to rationalize 'tmpfile is to consider #f to denote "invalid", in which case #f for the =E2=80=98tmpfile=E2=80=99 (the port-returning proc) d= oes not ring true. On the other hand, until another file-port with non-string filename type rears, i have no problem mentally keeping track of: (port-filename P) =3D> 'tmpfile =3D=3D=3D (and (file-port? P) (not (port-filename P))) except that =E2=80=98file-port?=E2=80=99 does not exist in Guile 1.4.x (ano= ther reason to hoof it over to official Guile :-). The bigger question is (to touch upon a past discussion) the separation of "file name" into "directory component + base name". If that ever comes to pass (fundamentally), i think =E2=80=98port-filename=E2=80=99 won't mind tr= ansparently passing the (richer) information to the user, with rv type most likely in the set {#f, string, location (d+b)}, with some distinguished locations symbolic. Then we can welcome the return of 'tmpfile. thi