all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 48133@debbugs.gnu.org, Amin Bandali <mab@gnu.org>
Subject: bug#48133: 28.0.50; [native-comp] time-to-days throws wrong-number-of-arguments error
Date: Sun, 02 May 2021 16:40:18 +0800	[thread overview]
Message-ID: <87r1ipbkb1.fsf@localhost> (raw)
In-Reply-To: <87h7jlilqb.fsf@gnus.org>

Lars Ingebrigtsen <larsi@gnus.org> writes:

> In this case, adding the additional optional arguments won't have an
> adverse effect in any Emacs version, I think?

Sure. I was thinking about more dramatic changes in argument list. Think
swapped args.

>> Is there any way to know in which Emacs version the function argument
>> list was changed?
>
> You'd have to ask git.

Fair enough. Though I was hoping for something like "Probably introduced
at or before Emacs version 19.29.", but for argument list. Or even
incorporating git changelog for given function into the help buffer.





  reply	other threads:[~2021-05-02  8:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-01  1:47 bug#48133: 28.0.50; [native-comp] time-to-days throws wrong-number-of-arguments error Ihor Radchenko
2021-05-01  6:33 ` Eli Zaretskii
2021-05-01  7:11   ` Ihor Radchenko
2021-05-01  7:54     ` Eli Zaretskii
2021-05-01  8:22       ` Ihor Radchenko
2021-05-01  8:27         ` Eli Zaretskii
2021-05-01 19:35         ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-02  7:18 ` Lars Ingebrigtsen
2021-05-02  7:43   ` Ihor Radchenko
2021-05-02  8:01     ` Lars Ingebrigtsen
2021-05-02  8:28       ` Ihor Radchenko
2021-05-02  8:27         ` Lars Ingebrigtsen
2021-05-02  8:40           ` Ihor Radchenko [this message]
2021-05-02  8:43             ` Lars Ingebrigtsen
2021-05-02 13:06       ` Ihor Radchenko
2021-05-02 13:04         ` 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

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

  git send-email \
    --in-reply-to=87r1ipbkb1.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=48133@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=mab@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.