From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Thomas Morley Newsgroups: gmane.lisp.guile.user Subject: Re: What's up with 'current-load-port' Date: Mon, 5 Nov 2018 10:49:30 +0100 Message-ID: References: <87a7momh8c.fsf@netris.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Trace: blaine.gmane.org 1541411294 20735 195.159.176.226 (5 Nov 2018 09:48:14 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 5 Nov 2018 09:48:14 +0000 (UTC) Cc: guile-user@gnu.org To: mhw@netris.org Original-X-From: guile-user-bounces+guile-user=m.gmane.org@gnu.org Mon Nov 05 10:48:10 2018 Return-path: Envelope-to: guile-user@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gJbUQ-0005I3-7x for guile-user@m.gmane.org; Mon, 05 Nov 2018 10:48:10 +0100 Original-Received: from localhost ([::1]:34202 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gJbWW-000723-AW for guile-user@m.gmane.org; Mon, 05 Nov 2018 04:50:20 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44720) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gJbW3-00071m-Aj for guile-user@gnu.org; Mon, 05 Nov 2018 04:49:52 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gJbW2-0002K2-4o for guile-user@gnu.org; Mon, 05 Nov 2018 04:49:51 -0500 Original-Received: from mail-wm1-x32c.google.com ([2a00:1450:4864:20::32c]:53953) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gJbW0-0001Jd-6u for guile-user@gnu.org; Mon, 05 Nov 2018 04:49:48 -0500 Original-Received: by mail-wm1-x32c.google.com with SMTP id v24-v6so7600206wmh.3 for ; Mon, 05 Nov 2018 01:49:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=BJpU6uHcgusqQEBkgcj8eDCeYI39DfpwIV9B86d4Xmc=; b=WQE1UKJjMFg8WWAL2jf26Wzr1l0cTtjGRIw1X6nPx2sK2uOTz3wnNjTn61XctpqEEv r9WmHOJBEj5g3CDElru40cPTgQE/QSZvKiHFGJVuNAZjDlDmzxUjlknrX3VPYCTKrxoo j33KvEvgWXT7uyZnTogD0xowuiMmsXDmkANl6nOknfTU9cbZaz6oWlPMBKzdmQPBcsHS ZFQamrn0Jv+7h/kupGjfmNdLAS/fzbjYlGJJPQlump5WNUl0S4zWOGL6KsLxofCLHhrL MNa4Rp9FPn4BtuNBylWNxNPXtkj6+aBMgzaVW4yG+qROtwAuERh+DP8+zepKkYCbroeO dFUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=BJpU6uHcgusqQEBkgcj8eDCeYI39DfpwIV9B86d4Xmc=; b=Elei04SSXDW898QoGuLCIgcN9tHEe7t8u6+dTV5xvsknCYY91ukSdAfYXDUC1U5zik toR+t67eS2aed0t9H9oUNpRsm44ym1CJICgWis2vwEdqKreKtYU220sa86mDEcKDmOzm dR2/NP+p/L2ROMUomsDfRdDWmskReenl2HcvRH9rfAVsuEZPRVzNR4A7BFg6I6IC/tKp Q0ycTIAM/bvn11XfXkHgg7k0izzjd2oJ9blq42EgbvbAhavlsnX2OGiu11o1aJEVG2p/ z2YITXGVWlhfQIcxcavA2T1n0SkwEm15sykv8EfAl/D6rS1GtV+WjRZky3U/f6EZ41ME L3Xw== X-Gm-Message-State: AGRZ1gIq2S+foxdvnnjcvxGVv8z8ydnZYQ7atV5xW5U5ssDFhwmZdr1c pWaUKZjAAQxeskydriXGrmFJ4Ktme4lQCzV+3AGfk9n7 X-Google-Smtp-Source: AJdET5dbKfR6xhpNvJ+jWHOhozVb4ImXyRzX8ov55/HhbBNwzMgxYvgzHvL7LqrFCXhoqM/vRprr7Ex6OqONdk8II7k= X-Received: by 2002:a1c:7fc1:: with SMTP id a184-v6mr5848785wmd.44.1541411385946; Mon, 05 Nov 2018 01:49:45 -0800 (PST) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:1450:4864:20::32c X-BeenThere: guile-user@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: General Guile related discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-user-bounces+guile-user=m.gmane.org@gnu.org Original-Sender: "guile-user" Xref: news.gmane.org gmane.lisp.guile.user:14963 Archived-At: Am Mo., 5. Nov. 2018 um 09:25 Uhr schrieb Thomas Morley : > > Am Mo., 5. Nov. 2018 um 02:43 Uhr schrieb Mark H Weaver : > > > > Thomas Morley writes: > > > > > what's up with 'current-load-port'? > > > > > > Simply checking in a guile-prompt I get: > > > guile-1.8: # > > > guile-2.0.14: # > > > guile-2.2.4 and guile-2.9.1: > > > ;;; : warning: possibly unbound variable `current-load-port' > > > ERROR: In procedure module-lookup: Unbound variable: current-load-port > > > > > > It's in the manual, though, without any hint it could be deprecated or > > > disabled or the need to use a certain module. > > > > Good catch. I agree that this was mishandled. > > > > Out of curiosity, what do you use 'current-load-port' for? > > > > Although it's in the manual, the description doesn't really describe > > what the procedure returns, or when one can rely upon it being set. It > > only says that it's "used internally by 'primitive-load'". > > > > Mark > > Some background: > You probably remember I'm from LilyPond. Currently we still use > guilev-1.8, though have experimental support for guilev2. > I do a lot of support on our user-list, frequently checking things > with my lilypond-guilev2-setup to detect bugs. > > Recently a user wrote a large scm-file and put it into lilypond using > '(load file.scm)'. > No problem with guilev1, but with guilev2 'file.scm' is not found. > Thus I tried to track the problem down. > Not a bad start is to rtfm :) > So I found 'current-load-port' and intended to play around with it > whether I can get some useful info out of it. > > In short, I likely don't need 'current-load-port' for anything, but > couldn't be sure before I used it. Thus this thread and patch. > > While doing rtfm I found 'primitive-load' working for the above > described purpose in guilev1 and guilev2. So the problem is solvable. > > Although this doesn't explain why 'load' stopped working for lilypond. > I then started from our master (guilev1) and changed only two things: > - teaching configure to accept guile-2.9.1 > - disabling a certain not longer supported function (only needed for > collecting some statistic data and never used afair) > Omitting all other guilev2-patches will ofcourse result in a very > buggy lilypond, if someone would intend to use it, but enough to check > whether 'load' works. > It does not. > So the underlying problem is either already in lilypond-master or > guilev2 changed something in 'load'. > > That's my current research-state. Addition: (load "full/path/to/file.scm") does work in LilyPond as opposed to a relative path. > > Any hint from the guile side? > > > Thanks, > Harm