all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: "Stefan Monnier" <monnier@iro.umontreal.ca>,
	"João Távora" <joaotavora@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: RE: Byte-compilation warning in eldoc.el
Date: Fri, 10 Jul 2020 08:05:58 -0700 (PDT)	[thread overview]
Message-ID: <1363dbd4-2132-404b-9a4a-1cc6ff625971@default> (raw)
In-Reply-To: <jwv4kqfbfo6.fsf-monnier+emacs@gnu.org>

> > Thanks, fixed.  But curiously it doesn't.  You can call it (and I
> > always do call it) with one argument, as one does in CL.
> 
> Technically, you can call it with one argument.
> But in 99% of the cases it's a really bad idea.

Why?  What are those 99% (or what is the 1%)?
What's the (undocumented) behavior of calling it
with no second arg?  Isn't it just to use the
value of `obarray' (the standard obarray)?

What's the reason that the 2nd arg isn't called
out as optional, with the doc string saying that
it defaults to the value of variable `obarray'?

What's good about having an optional parameter
that's not advertised as such?  What's the real
point here, that calls for this exception?



  reply	other threads:[~2020-07-10 15:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-10  6:53 Byte-compilation warning in eldoc.el Eli Zaretskii
2020-07-10  7:20 ` João Távora
2020-07-10  7:43   ` Eli Zaretskii
2020-07-10  9:36   ` Noam Postavsky
2020-07-10 14:41   ` Stefan Monnier
2020-07-10 15:05     ` Drew Adams [this message]
2020-07-10 15:31     ` João Távora
2020-07-10 21:29       ` Stefan Monnier
2020-07-10 21:48         ` João Távora
2020-07-10 22:08           ` 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=1363dbd4-2132-404b-9a4a-1cc6ff625971@default \
    --to=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    /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.