From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Jose A. Ortega Ruiz" Newsgroups: gmane.lisp.guile.devel Subject: Re: [PATCH] Fix for `submodules' in (ice-9 session) (closes #30062) Date: Thu, 02 Sep 2010 01:30:08 +0200 Message-ID: <87pqwxyrcv.fsf@newton.homeunix.net> References: <1283257143-24354-1-git-send-email-jao@gnu.org> <87occi34ry.fsf@newton.homeunix.net> <87bp8i2x9e.fsf@newton.homeunix.net> <877hj5r7rt.fsf@gnu.org> <87y6blyyec.fsf@newton.homeunix.net> <87k4n5ksr7.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: dough.gmane.org 1283386116 10103 80.91.229.12 (2 Sep 2010 00:08:36 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 2 Sep 2010 00:08:36 +0000 (UTC) To: guile-devel@gnu.org Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Thu Sep 02 02:08:35 2010 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 1OqxM1-0006NH-FX for guile-devel@m.gmane.org; Thu, 02 Sep 2010 02:08:34 +0200 Original-Received: from localhost ([127.0.0.1]:59093 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OqxLt-0002e5-H8 for guile-devel@m.gmane.org; Wed, 01 Sep 2010 20:08:25 -0400 Original-Received: from [140.186.70.92] (port=60070 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OqxLp-0002cK-7o for guile-devel@gnu.org; Wed, 01 Sep 2010 20:08:22 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OqxLn-00053I-6O for guile-devel@gnu.org; Wed, 01 Sep 2010 20:08:20 -0400 Original-Received: from lo.gmane.org ([80.91.229.12]:56649) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OqxLm-00052c-RC for guile-devel@gnu.org; Wed, 01 Sep 2010 20:08:19 -0400 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1OqxLj-0006Ha-R1 for guile-devel@gnu.org; Thu, 02 Sep 2010 02:08:15 +0200 Original-Received: from 83.50.71.238 ([83.50.71.238]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 02 Sep 2010 02:08:15 +0200 Original-Received: from jao by 83.50.71.238 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 02 Sep 2010 02:08:15 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 48 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 83.50.71.238 User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) X-Attribution: jao X-URL: Cancel-Lock: sha1:VlYXCNsvOCR8uRSDPwuwQ10vLfE= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) 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:10834 Archived-At: Hi Ludo, On Thu, Sep 02 2010, Ludovic Courtès wrote: > Hello! > [...] >>> psyntax expects modules to have a name so that it can refer to them in >>> expanded code. Thus, there can be no anonymous modules: modules are >>> always given a name, see ‘module-name’. This allows things like the >>> “compile in fresh module” test to work. >> >> I see. But then, aren't those modules something internal to psyntax's >> workings? > > No, they’re not internal. They’re just (pseudo-)anonymous modules that > ended up in the module hierarchy, like any other module. Evaluate > (module-name (make-module)) and you’ve added another one. :-) Oh, i see. (Then, i could/should probably test anonymous modules in the new session.test too.) >> And if so, shouldn't they be filtered out from the return value of >> module-submodules (or not be traversed by the apropos-fold)? As a user >> of those procedures, i find the appearance of those modules a bit >> confusing (the only use case in client code i can think of is when >> using the return value of current-module). Am i missing something? > > I agree that as users we’d rather not see these modules, especially from > Geiser. But they have to be there. > > So, unless I’m missing an elegant design trick to avoid this, I think > you’re bound to use heuristics to filter them out (e.g., get rid of > modules whose name contains white spaces.) Well, something along those lines is what Geiser is actually doing right now :) Thanks for the clarification. Cheers, jao -- Genius may have its limitations, but stupidity is not thus handicapped. -Elbert Hubbard