Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | ruby: Rename destroy to destroy! | Ali Polatel | 2011-09-24 |
| | | | | | | | | | | | | | | | | | According to the common Ruby function naming convention, potentially dangerous functions or functions which operate on the object itself are suffixed with an exclamation mark. Both of these are true for object destroying functions. The following modules are affected: - Notmuch::Directory - Notmuch::FileNames - Notmuch::Query - Notmuch::Threads - Notmuch::Thread - Notmuch::Messages - Notmuch::Message - Notmuch::Tags | ||
* | ruby: Don't barf if an object is destroyed more than once | Ali Polatel | 2010-06-06 |
| | | | | | | Raise RuntimeError instead. Also revise Notmuch::Database a bit. Add Notmuch::Database.open singleton method. | ||
* | ruby: Kill garbage collection related cruft. | Ali Polatel | 2010-06-06 |
| | | | | | | | Let the user destroy objects that she wants explicitly. It's not possible to specify the order objects are garbage collected. See id:86y6f8v838.fsf@harikalardiyari.ev on ruby-talk for more information. | ||
* | Initial ruby bindings | Ali Polatel | 2010-06-06 |