unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Shiyao Ma <i@introo.me>, 22066@debbugs.gnu.org
Subject: bug#22066: 24.5; documentation for "values" is not accurate
Date: Tue, 09 Feb 2021 10:24:04 -0500	[thread overview]
Message-ID: <jwvo8gts1zw.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <875z31lllw.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 09 Feb 2021 08:57:15 +0100")

>> Yup.  I've now done this on the trunk, and I'm marking `values' as
>> obsolete (after doing some more testing).
> Actually, I can't really mark `values' as obsolete, because that makes
>
> (let (values)
>   ...
>   values)
>
> issue a warning...

The same problem affects `pi`.  For this reason it's declared obsolete
in NEWS and in its docstring but not with `make-obsolete` :-(

Maybe we should change the byte-compiler so it doesn't issue
obsolescence warnings when the variable is lexically scoped?

So we'd issue a warning for

    ... values ...

but not for

    (let ((values ...)) ... values ...)

?


        Stefan






  reply	other threads:[~2021-02-09 15:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-01  5:48 bug#22066: 24.5; documentation for "values" is not accurate Shiyao Ma
2019-08-01 17:21 ` Lars Ingebrigtsen
2021-02-08  7:16   ` Lars Ingebrigtsen
2021-02-08 16:00     ` Stefan Monnier
2021-02-08 16:15       ` Lars Ingebrigtsen
2021-02-08 17:07         ` Stefan Monnier
2021-02-09  7:37           ` Lars Ingebrigtsen
2021-02-09  7:57             ` Lars Ingebrigtsen
2021-02-09 15:24               ` Stefan Monnier [this message]
2021-02-09 15:26                 ` Lars Ingebrigtsen
2021-02-09 18:29                   ` Stefan Monnier
2021-02-09 18:32                     ` Lars Ingebrigtsen
2021-02-09 18:33                       ` Lars Ingebrigtsen
2021-02-09 20:29                         ` Stefan Monnier
2021-02-09 18:35                       ` Lars Ingebrigtsen

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=jwvo8gts1zw.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=22066@debbugs.gnu.org \
    --cc=i@introo.me \
    --cc=larsi@gnus.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).