From: manday@openmail.cc
To: guile-devel@gnu.org
Subject: Loss of location in (library) code
Date: Sat, 14 Nov 2020 20:26:13 +0100 [thread overview]
Message-ID: <20201114192613.GA4924@air> (raw)
As discussed on #guile, we tried for a "possibly unbound variable" warning, on Guile 3.0.4:
When the offending form is somewhere in a RnRS module or Guile library, the warnings give inconsistent line numbers. For instance:
(library (test)
(export f)
(import (rnrs))
(define (f x)
(if x
(cons x 3)
(IS-UNBOUND x))))
produces "4:1: warning: possibly unbound variable `IS-UNBOUND'", the warning is located on the (define) whereas
; Line 1
; Line 2
; Line 3
(define (f x)
(if x
(cons x 3)
(IS-UNBOUND x)))
produces "7:2: warning: possibly unbound variable `IS-UNBOUND'", the warning is located correctly.
-------------------------------------------------
This free account was provided by VFEmail.net - report spam to abuse@vfemail.net
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!
next reply other threads:[~2020-11-14 19:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-14 19:26 manday [this message]
2020-11-14 19:36 ` Loss of location in (library) code manday
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201114192613.GA4924@air \
--to=manday@openmail.cc \
--cc=guile-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).