[Xapian-tickets] [Xapian] #504: Add is_closed() to Database class

[Xapian]

#504: Add is_closed() to Database class
-----------------------------+----------------------------------------------
 Reporter:  jcassee          |       Owner:  olly
     Type:  enhancement      |      Status:  new 
 Priority:  normal           |   Milestone:      
Component:  Xapian-bindings  |     Version:      
 Severity:  minor            |    Keywords:      
Blockedby:                   |    Platform:  All 
 Blocking:                   |  
-----------------------------+----------------------------------------------

Comment(by olly):

 I adjusted the documentation comment for {{{Database::close()}}} in r15893
 to tone down the warning a bit, and also added a rationale for why we have
 this behaviour.

 jcassee: The time required to implement isn't a big issue (though it is a
 consideration).  My main concern is that the more methods a class has, the
 harder it is for users to get to grips with using it - the cost of a new
 method is that it makes the class a little harder to comprehend.  As
 Richard says, my experience is that it's easy to track this outside Xapian
 (generally you actually have a single handle on the Database and can just
 set it to NULL/undef/nil/etc after you close it).

 dcolish: How would you implement an {{{is_closed()}}} type method in the
 bindings or a client library without support in the C++ API?

-- 
Ticket URL: <http://trac.xapian.org/ticket/504#comment:5>
Xapian <http://xapian.org/>
Xapian