From: Sebastian Spaeth <Sebastian@SSpaeth.de>
To: Austin Clements <amdragon@MIT.EDU>,
Justus Winter <4winter@informatik.uni-hamburg.de>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH 7/7] python: wrap and use notmuch_database_destroy as destructor
Date: Fri, 20 Apr 2012 15:10:04 +0200 [thread overview]
Message-ID: <87ty0ek0r7.fsf@sspaeth.de> (raw)
In-Reply-To: <20120412170249.GG13549@mit.edu>
[-- Attachment #1: Type: text/plain, Size: 425 bytes --]
Austin Clements <amdragon@MIT.EDU> writes:
> (I think it also doesn't make sense to expose notmuch_database_destroy
> as a general, public method since it will free all of the other C
> objects out from under the bindings, resulting in exactly the double
> free-type crashes that you're trying to avoid. It appears that none
> of the other Python classes have a destroy method.)
Agreed, that sounds right to me.
Sebastian
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2012-04-21 11:22 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 0:55 [RFC] Split notmuch_database_close into two functions Justus Winter
2012-03-21 0:55 ` [PATCH 1/7] " Justus Winter
2012-03-31 17:17 ` Mark Walters
2012-03-31 17:29 ` David Bremner
2012-04-16 21:51 ` Justus Winter
2012-04-17 8:37 ` Mark Walters
2012-03-21 0:55 ` [PATCH 2/7] NEWS: Document the notmuch_database_close split Justus Winter
2012-03-21 0:55 ` [PATCH 3/7] Use notmuch_database_destroy instead of notmuch_database_close Justus Winter
2012-03-21 0:55 ` [PATCH 4/7] " Justus Winter
2012-03-21 0:55 ` [PATCH 5/7] go: " Justus Winter
2012-03-21 0:55 ` [PATCH 6/7] ruby: " Justus Winter
2012-03-21 0:55 ` [PATCH 7/7] python: wrap and use notmuch_database_destroy as destructor Justus Winter
2012-04-12 17:02 ` Austin Clements
2012-04-20 13:10 ` Sebastian Spaeth [this message]
2012-04-22 12:06 ` Justus Winter
2012-04-22 12:07 ` [PATCH 1/7] Split notmuch_database_close into two functions Justus Winter
2012-04-22 12:07 ` [PATCH 2/7] NEWS: Document the notmuch_database_close split Justus Winter
2012-04-22 15:09 ` Felipe Contreras
2012-04-22 12:07 ` [PATCH 3/7] Use notmuch_database_destroy instead of notmuch_database_close Justus Winter
2012-04-22 12:07 ` [PATCH 4/7] " Justus Winter
2012-04-22 12:07 ` [PATCH 5/7] go: " Justus Winter
2012-04-22 12:07 ` [PATCH 6/7] ruby: " Justus Winter
2012-04-23 12:36 ` Felipe Contreras
2012-04-23 12:49 ` Justus Winter
2012-04-25 13:39 ` Austin Clements
2012-04-22 12:07 ` [PATCH 7/7] python: wrap and use notmuch_database_destroy as destructor Justus Winter
2012-04-22 18:01 ` [PATCH 1/7] Split notmuch_database_close into two functions Austin Clements
2012-04-25 13:20 ` Justus Winter
2012-04-25 13:34 ` Austin Clements
2012-04-28 12:54 ` David Bremner
2012-04-22 18:06 ` Austin Clements
2012-03-21 8:57 ` [RFC] " Patrick Totzke
2012-03-24 9:07 ` Tomi Ollila
2012-03-27 8:19 ` Justus Winter
2012-03-27 8:19 ` [PATCH 1/7] " Justus Winter
2012-04-01 3:23 ` [RFC] " Austin Clements
2012-04-12 9:05 ` Justus Winter
2012-04-12 16:57 ` Austin Clements
2012-04-12 17:19 ` Justus Winter
[not found] ` <20120413083358.13321.66680@megatron>
2012-04-16 21:45 ` Justus Winter
2012-04-17 4:56 ` Tomi Ollila
2012-04-17 8:42 ` Mark Walters
2012-04-18 17:54 ` Austin Clements
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ty0ek0r7.fsf@sspaeth.de \
--to=sebastian@sspaeth.de \
--cc=4winter@informatik.uni-hamburg.de \
--cc=amdragon@MIT.EDU \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).