all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: tramp-compat-funcall -> compat-funcall?
Date: Sat, 24 Sep 2016 18:42:20 -0400	[thread overview]
Message-ID: <87y42gyl6b.fsf@lifelogs.com> (raw)
In-Reply-To: jwv60plbduu.fsf-monnier+Inbox@gnu.org

On Sat, 24 Sep 2016 09:57:32 -0400 Stefan Monnier <monnier@iro.umontreal.ca> wrote: 

>>> There's  (if (fboundp '<foo>) (<foo> <bar>))  already (which is much
>> Your code snippet misses the `with-no-warnings' umbrella.

SM> No, it doesn't: the byte-compiler understands the the if+fboundp means
SM> that any call to this function in the branch is "safe" and it won't
SM> signal a warning.  That's my point.

I didn't know that. Thanks for explaining. I think the Gnus function
`gnus-funcall-no-warning' can be safely removed then? It's only in three
places, so it's an easy fix, but I want to check in case I missed something.

Ted




  parent reply	other threads:[~2016-09-24 22:42 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
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 [this message]
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

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

  git send-email \
    --in-reply-to=87y42gyl6b.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.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.