unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Robert Irelan <rirelan@gmail.com>
Cc: Phil Sainty <psainty@orcon.net.nz>,
	"Basil L. Contovounesios" <contovob@tcd.ie>,
	46958@debbugs.gnu.org
Subject: bug#46958: 28.0.50; invalid-function error for macros that have function bindings
Date: Mon, 20 Jun 2022 03:10:53 +0200	[thread overview]
Message-ID: <87mte8qgv6.fsf@gnus.org> (raw)
In-Reply-To: <CAJUyYjo4DF-toBadm-745b660hMSJTsSsjkbn4F-js6Xb24GNw@mail.gmail.com> (Robert Irelan's message of "Sun, 7 Mar 2021 23:18:15 -0800")

Robert Irelan <rirelan@gmail.com> writes:

> Therefore, it looks like this is not a new bug in Emacs. It would be
> nice if, when an invalid-function is thrown from bytecode, to check
> the runtime environment to see a macro with the same name is defined,
> and print a more informative error pointing out an issue with the
> compilation.

(I'm going through old bug reports that unfortunately weren't resolved
at the time.)

I'm not sure there's much to be done here on the Emacs side.  When you
compiled the file, you should have gotten a byte compilation warning
about the macro not being defined.  The runtime error (about funcalling
the macro) could be expanded, of course, to something like "invalid
function (probably a missing byte compilation `require')" or something,
but I don't think that'd add a lot of value -- since you only get into
this situation by ignoring the byte compiler warning in the first case.

So I'm closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2022-06-20  1:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-06  2:00 bug#46958: 28.0.50; invalid-function error for macros that have function bindings Robert Irelan
2021-03-06 12:55 ` Lars Ingebrigtsen
2021-03-06 14:24   ` Basil L. Contovounesios
2021-03-06 18:28     ` Robert Irelan
2021-03-06 22:39       ` Phil Sainty
2021-03-07 14:27         ` Basil L. Contovounesios
2021-03-07 21:38         ` Robert Irelan
2021-03-08  6:30           ` Phil Sainty
2021-03-08  7:18             ` Robert Irelan
2021-03-08  9:06               ` Phil Sainty
2022-06-20  1:10               ` Lars Ingebrigtsen [this message]
2021-03-07 14:33   ` Pip Cet
2021-03-07 15:58     ` Lars Ingebrigtsen
2021-03-07 18:06       ` Pip Cet

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/emacs/

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

  git send-email \
    --in-reply-to=87mte8qgv6.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=46958@debbugs.gnu.org \
    --cc=contovob@tcd.ie \
    --cc=psainty@orcon.net.nz \
    --cc=rirelan@gmail.com \
    /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 public inbox

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

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).