From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Andy Wingo Newsgroups: gmane.lisp.guile.devel Subject: Re: [PATCH 2/5] [mingw]: Have compiled-file-name produce valid names. Date: Sun, 01 May 2011 23:12:09 +0200 Message-ID: References: <1297784103-18322-1-git-send-email-janneke-list@xs4all.nl> <1297784103-18322-3-git-send-email-janneke-list@xs4all.nl> 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 1304284354 11455 80.91.229.12 (1 May 2011 21:12:34 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 1 May 2011 21:12:34 +0000 (UTC) Cc: Jan Nieuwenhuizen , guile-devel@gnu.org To: Noah Lavine Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Sun May 01 23:12:30 2011 Return-path: Envelope-to: guile-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QGdwE-0003t0-Lm for guile-devel@m.gmane.org; Sun, 01 May 2011 23:12:22 +0200 Original-Received: from localhost ([::1]:56242 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QGdwE-00059U-4k for guile-devel@m.gmane.org; Sun, 01 May 2011 17:12:22 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:50429) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QGdwC-00059M-2x for guile-devel@gnu.org; Sun, 01 May 2011 17:12:20 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QGdwA-0007DW-TA for guile-devel@gnu.org; Sun, 01 May 2011 17:12:20 -0400 Original-Received: from a-pb-sasl-sd.pobox.com ([64.74.157.62]:42453 helo=sasl.smtp.pobox.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QGdwA-0007D5-OQ for guile-devel@gnu.org; Sun, 01 May 2011 17:12:18 -0400 Original-Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by a-pb-sasl-sd.pobox.com (Postfix) with ESMTP id 201985A0A; Sun, 1 May 2011 17:14:22 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type:content-transfer-encoding; s=sasl; bh=AFiWTHo5aqIr ghh5Nken8jrzOkk=; b=LIvKZ28v0WV27RkYenG/nJFv6nAqPjd9yXWQUjAJBYCd yc0JUC1q6txQhkMNSvOPo1PMyeJ99ji7iZPqN+VkdLAeGTgiPWysJWgbUNo+V3wf 9AUaMjdYFQSTPD4UycOSFWi3mfcHEGI6f5olaxNmoYStHfhgX7V/wBmSmNhaAbk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type:content-transfer-encoding; q=dns; s=sasl; b=TpyzTF /ysI+Ny/sbVgFHlFD0ocP/vojhi8AG/1yZNac52V8ZeuCs7P1bMYroEzFj8KdhUs CRO3bJop29MGrD8PafTIZek8V1aGauBo/K1zktXZ+CjEGVa9iDbNqkHKNt8u1YMR seM0qFM0T/bTMWVTNRUQs3FioNRj4QJVv4/Rg= Original-Received: from a-pb-sasl-sd.pobox.com (unknown [127.0.0.1]) by a-pb-sasl-sd.pobox.com (Postfix) with ESMTP id F1D945A02; Sun, 1 May 2011 17:14:18 -0400 (EDT) Original-Received: from unquote.localdomain (unknown [90.164.198.39]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by a-pb-sasl-sd.pobox.com (Postfix) with ESMTPSA id 0CFBA5A01; Sun, 1 May 2011 17:14:15 -0400 (EDT) In-Reply-To: (Noah Lavine's message of "Sun, 1 May 2011 15:23:41 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) X-Pobox-Relay-ID: FA197D5E-7437-11E0-A7C9-E8AB60295C12-02397024!a-pb-sasl-sd.pobox.com X-detected-operating-system: by eggs.gnu.org: Solaris 10 (beta) X-Received-From: 64.74.157.62 X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Original-Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.devel:12395 Archived-At: Hi, On Sun 01 May 2011 21:23, Noah Lavine writes: >> Yep! =C2=A0Check that racket web page I linked to. =C2=A0You don't have = to >> implement all of it, but it should be possible to implement, given the >> path abstraction. > > Okay, I've read it. It doesn't seem very complicated. Should we strive > for API compatibility? I don't see any programs needing it right now, > but maybe there would be in the future if we made them compatible. I don't think we need to be compatible, no. That said it does look pretty good. > I think of a path as a vector of "path elements", each of which > represents a directory except that the last one might represent a > file. I notice the Racket path library makes their path object > distinct from this - you can build a path from a list of path elements > with build-path, and turn a path into a list of path elements with > explode-path, but you can't take an actual path object and manipulate > its components (unless I've missed something). Do you think this is > the right way to think of it? I think that might be what you want sometimes, but it doesn't correspond to the underlying OS path concept. You could build such a thing on top of the byte arrays, but I don't think a vector (or list, ...) is always going to be what you want. I don't know. I would say to stick with byte arrays and strings on the lowest level. Cheers, Andy --=20 http://wingolog.org/