From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Dmitry Antipov <antipov@mvista.com>, emacs-devel@gnu.org
Subject: Re: A question about struct coding_system
Date: Mon, 21 Nov 2011 15:22:34 -0500 [thread overview]
Message-ID: <jwvy5v9usz6.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <m24nxx76uu.fsf@igel.home> (Andreas Schwab's message of "Mon, 21 Nov 2011 17:55:37 +0100")
> It's generally the duty of the caller to protect the object.
No, Emacs's C code generally puts the burden on the callee rather than
the caller (with a few exceptions like Ffuncall).
Stefan
next prev parent reply other threads:[~2011-11-21 20:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 16:13 A question about struct coding_system Dmitry Antipov
2011-11-21 16:55 ` Andreas Schwab
2011-11-21 20:22 ` Stefan Monnier [this message]
2011-11-21 20:32 ` Andreas Schwab
2011-11-21 17:47 ` 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
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=jwvy5v9usz6.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=antipov@mvista.com \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.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).