From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 27178@debbugs.gnu.org, npostavs@gmail.com, eefacm@gmail.com
Subject: bug#27178: 26.0.50; libxml-parse-*-region functions ignore discard-comments argument
Date: Sat, 14 Apr 2018 18:35:01 +0300 [thread overview]
Message-ID: <83h8od4x96.fsf@gnu.org> (raw)
In-Reply-To: <8736zxizjg.fsf@mouse.gnus.org> (message from Lars Ingebrigtsen on Sat, 14 Apr 2018 17:21:55 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, 27178@debbugs.gnu.org, eefacm@gmail.com
> Date: Sat, 14 Apr 2018 17:21:55 +0200
>
> Noam Postavsky <npostavs@gmail.com> writes:
>
> > I think we have advertised-calling-convention for this:
> >
> > `(advertised-calling-convention SIGNATURE WHEN)'
> > This acts like a call to `set-advertised-calling-convention'
> > (*note Obsolete Functions::); SIGNATURE specifies the correct
> > argument list for calling the function or macro, and WHEN
> > should be a string indicating when the old argument list was
> > first made obsolete.
>
> Ah, thanks.
>
> That's as a declaration in the defun? How would we do this for a
> built-in C function, then? Hm...
Doesn't set-advertised-calling-convention work on primitives?
There's also the "usage:" thingie.
next prev parent reply other threads:[~2018-04-14 15:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 0:07 bug#27178: 26.0.50; libxml-parse-*-region functions ignore discard-comments argument Sean McAfee
2017-06-10 15:50 ` npostavs
2018-04-13 22:54 ` Lars Ingebrigtsen
2018-04-14 6:49 ` Eli Zaretskii
2018-04-14 13:11 ` Lars Ingebrigtsen
2018-04-14 13:28 ` Eli Zaretskii
2018-04-14 13:54 ` Lars Ingebrigtsen
2018-04-14 15:00 ` Eli Zaretskii
2018-04-14 15:14 ` Lars Ingebrigtsen
2018-04-14 15:17 ` Noam Postavsky
2018-04-14 15:21 ` Lars Ingebrigtsen
2018-04-14 15:35 ` Eli Zaretskii [this message]
2018-04-14 15:43 ` Lars Ingebrigtsen
2018-04-14 16:24 ` Eli Zaretskii
2018-04-14 15:35 ` Noam Postavsky
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=83h8od4x96.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=27178@debbugs.gnu.org \
--cc=eefacm@gmail.com \
--cc=larsi@gnus.org \
--cc=npostavs@gmail.com \
/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).