static variable cleanup

Subject: static variable cleanup

Date: Thu, 13 May 2021 07:07:03 -0300

To: notmuch@notmuchmail.org

Cc:

From: David Bremner

Both the library and the CLI use a fair amount of static
variables. These are an obvious blocker for any kind of thread-safety,
even the limited goal of concurrently opening two databases for
reading in the same process.  This series cleans up some of the
low-hanging fruit.

_______________________________________________
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-leave@notmuchmail.org

• Previous message (by thread): Re: [PATCH 6/7] CLI: make static message strings const

Thread:

• David Bremner—static variable cleanup [inbox, unread]
  • David Bremner—[PATCH 1/7] lib: make glib initialization thread-safe [inbox, notmuch::patch, notmuch::pushed, unread]
  • David Bremner—[PATCH 2/7] lib/generate_thread_id: move static buffer to notmuch_database_t [inbox, notmuch::patch, notmuch::pushed, unread]
  • David Bremner—[PATCH 3/7] lib/message: mark flag2tag as const [inbox, notmuch::patch, notmuch::pushed, unread]
  • David Bremner—[PATCH 4/7] CLI: centralize initialization in notmuch_client_init [inbox, notmuch::patch, notmuch::pushed, unread]
  • David Bremner—[PATCH 5/7] CLI/config: make immutable tables const [inbox, notmuch::patch, notmuch::pushed, unread]
  • David Bremner—[PATCH 6/7] CLI: make static message strings const [inbox, notmuch::patch, notmuch::pushed, unread]
    • Tomi Ollila—Re: [PATCH 6/7] CLI: make static message strings const [inbox, unread]
      • David Bremner—Re: [PATCH 6/7] CLI: make static message strings const [inbox, unread]
        • Tomi Ollila—Re: [PATCH 6/7] CLI: make static message strings const [inbox, unread]
  • David Bremner—[PATCH 7/7] CLI/notmuch: make immutable tables const [inbox, notmuch::patch, notmuch::pushed, unread]