unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: emacs-devel@gnu.org
Subject: Re: Should `indirect-function' be preferred over `fboundp'?
Date: Fri, 21 Jul 2023 03:08:28 +0200	[thread overview]
Message-ID: <87cz0mul4j.fsf@web.de> (raw)
In-Reply-To: 87h6pzxdof.fsf@localhost

Ihor Radchenko <yantar92@posteo.net> writes:

> (I can see that `fboundp' is used all over Emacs git sources, while
> `indirect-function' is rarely used)

I'm actually not that surprised.  I guess, most often code using an
`fboundp' test wants to test whether a function has already been defined
(e.g. by another package), or is available in the current Emacs version.

An alias is a definition.  In most cases the definition as an alias is
intentional.  If an alias points to an undefined function, I guess that,
in the majority of cases, this hints at some kind of problem so it's
better to have an error rather than to circumvent the problem by using
`indirect-function'.

Are aliases to undefined functions something to expect often?  The
compiler warns in the case when the DEFINITION is the name of an unknown
function.  It should be the responsibility of the alias creating code to
ensure that the alias is not broken.


Michael.




  parent reply	other threads:[~2023-07-21  1:08 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 [this message]
2023-07-21  6:07   ` Ihor Radchenko
2023-07-22  2:49     ` Michael Heerdegen
2023-07-22 10:51       ` Ihor Radchenko
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=87cz0mul4j.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=emacs-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.
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).