unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: emacs-devel@gnu.org
Subject: Re: Should `indirect-function' be preferred over `fboundp'?
Date: Sat, 22 Jul 2023 10:51:44 +0000	[thread overview]
Message-ID: <878rb88bi7.fsf@localhost> (raw)
In-Reply-To: <87lef8wthm.fsf@web.de>

Michael Heerdegen <michael_heerdegen@web.de> writes:

>> I think that part of the problem _for me_ is that
>>
>> (defalias 'yant/foo 'yant/bar)
>> (fboundp 'yant/foo) ; => t
>> (funcall 'yant/foo) ; => ERROR: Symbol function definition is void: yant/foo
>>
>> only shows an error for `yant/foo', which is somewhat confusing.
>> `yant/bar' is where function definition is truly void.
>
> I see and understand.  The error message can be misleading in this case.

Would it be of interest to add 2 new error types:
1. Qvoid_indirect_function
2. Qinvalid_indirect_function

It will make it more explicit that it is function indirection that has
problems.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>



  reply	other threads:[~2023-07-22 10:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-20  7:08 Should `indirect-function' be preferred over `fboundp'? Ihor Radchenko
2023-07-20  7:42 ` Eli Zaretskii
2023-07-20  8:23   ` Ihor Radchenko
2023-07-20  7:47 ` Andreas Schwab
2023-07-20  8:25   ` Ihor Radchenko
2023-07-20 13:02 ` Alan Mackenzie
2023-07-20 13:08   ` Ihor Radchenko
2023-07-21  1:08 ` Michael Heerdegen
2023-07-21  6:07   ` Ihor Radchenko
2023-07-22  2:49     ` Michael Heerdegen
2023-07-22 10:51       ` Ihor Radchenko [this message]
2023-07-23  2:37         ` Michael Heerdegen

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=878rb88bi7.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-devel@gnu.org \
    --cc=michael_heerdegen@web.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 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).