From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: tramp-compat-funcall -> compat-funcall?
Date: Thu, 22 Sep 2016 16:18:17 -0400 [thread overview]
Message-ID: <87h997u1rq.fsf@lifelogs.com> (raw)
In-Reply-To: jwveg4cdsv2.fsf-monnier+gmane.emacs.devel@gnu.org
On Thu, 22 Sep 2016 08:31:22 -0400 Stefan Monnier <monnier@iro.umontreal.ca> wrote:
SM> I think hiding this behind (tramp-)compat-funcall would be better
SM> avoided (just like using with-no-warnings should be avoided whenever
SM> possible).
SM> IOW, if there's a kind of situation that recurs often enough to warrant
SM> something like (tramp-)compat-funcall you should report this as a bug.
The use case, I think, is "to provide compatibility with older Emacsen,
I need a convenient way to call a function softly without compiler
warnings if it doesn't exist." I think, based on the two examples I gave
(`gnus-funcall-no-warning' was the other instance), that it's not an
uncommon need, and it's better to provide it in a core facility than ask
package maintainers to implement it.
If the use case is misguided, then what's the right way to call
functions that are missing in 25.1 but are needed in 24.3 for example?
Do we need a layered cond-like funcall instead, which tries several
invocations (not necessarily with the same arguments) until one
succeeds? In either case, the compiler warnings seem better silenced
than active, unless none of the cases succeed.
Ted
next prev parent reply other threads:[~2016-09-22 20:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 11:04 tramp-compat-funcall -> compat-funcall? Ted Zlatanov
2016-09-22 12:31 ` Stefan Monnier
2016-09-22 13:22 ` Michael Albinus
2016-09-22 17:46 ` Stefan Monnier
2016-09-22 17:54 ` Michael Albinus
2016-09-22 18:23 ` Stefan Monnier
2016-09-22 20:18 ` Ted Zlatanov [this message]
2016-09-23 15:49 ` Stefan Monnier
2016-09-24 6:54 ` Michael Albinus
2016-09-24 13:57 ` Stefan Monnier
2016-09-24 15:39 ` Michael Albinus
2016-09-24 18:40 ` Stefan Monnier
2016-09-25 11:44 ` Michael Albinus
2016-09-25 14:00 ` Stefan Monnier
2016-09-25 17:23 ` Ted Zlatanov
2016-09-24 22:42 ` Ted Zlatanov
2016-09-25 14:17 ` Stefan Monnier
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=87h997u1rq.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).