all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: 46241@debbugs.gnu.org
Cc: bug-guile@gnu.org, jbranso@dismail.de
Subject: bug#46241: Guile Macros did not print the error-line-number ?
Date: Fri, 19 Feb 2021 16:14:07 +0100	[thread overview]
Message-ID: <877dn4m6o0.fsf@gnu.org> (raw)
In-Reply-To: <87r1lzodwl.fsf@dismail.de> (jbranso's message of "Mon, 01 Feb 2021 13:12:42 -0500")

Hi Joshua,

jbranso--- via Bug reports for GNU Guix <bug-guix@gnu.org> skribis:

> Recently on irc, I posted an example of an incorrectly used
> define-record-type* NOT displaying an error line number.
>
> mdevos mentioned that this could potentially be fixed in (guix
> records), but it may also be a guile compile bug as well.
>
> First here is a (guix records) example:
>
> #+BEGIN_SRC scheme
> (use-modules (guix records))
>
> (define-record-type* <sway-bindsym>
>   sway-bindsym make-sway-bindsym
>   sway-bindsym?
>   (key-combo sway-bindsym-key-combo
>              (default "")))
>
> (display sway-bindsym)  ;; compile error at unknown location
> ;; (display (sway-bindsym))  this is one "correct" way to call this code
> #+END_SRC

Source location info is missing because currently (as of 3.0.5), Guile
keeps location info in the form of “source properties” only for lists.
The ‘sway-bindsym’ symbol above has no associated location info.

This may change in the near future as Andy has been rewriting ‘read’
(the Scheme “parser”) in Scheme, among other things.

Ludo’.




      reply	other threads:[~2021-02-19 15:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-01 18:12 bug#46241: Guile Macros did not print the error-line-number ? jbranso--- via Bug reports for GNU Guix
2021-02-19 15:14 ` Ludovic Courtès [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877dn4m6o0.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=46241@debbugs.gnu.org \
    --cc=bug-guile@gnu.org \
    --cc=jbranso@dismail.de \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.