BIND 10 #602: provide dummy locks instead of those in boost/thread
BIND 10 Development
do-not-reply at isc.org
Wed Feb 23 22:27:56 UTC 2011
#602: provide dummy locks instead of those in boost/thread
-------------------------------------+-------------------------------------
Reporter: jelte | Owner: UnAssigned
Type: defect | Status: reviewing
Priority: major | Milestone: R-Team-
Component: | Sprint-20110308
Unclassified | Resolution:
Keywords: | Sensitive: 0
Estimated Number of Hours: 0.0 | Add Hours to Ticket: 0
Billable?: 1 | Total Hours: 0
Internal?: 0 |
-------------------------------------+-------------------------------------
Changes (by jelte):
* owner: => UnAssigned
* status: new => reviewing
Comment:
two more additions; an important small one:
57b77aa7c09f568a9adf7f9ad475cc80f278fedc removes the boost/thread
inclusion from nameserver_address_store.cc as well
another one does a lot of actual cleanup in inclusion; this is not
strictly necessary, but should prevent future problems for a part;
48846bf7b70cc48e317aabc554a4dacef89b2d46 includes <config.h> in all cc
files that have includes that lead to the new locks.h (which should be
either some specific nsas things, or the broad asiolink.h), and the
headers that need asiolink functions include the specific headers for
that, instead of the general asiolink. The last commit removes the second
TODO (which is done by this), but leaves in the first; i'm not sure yet
whether we should check if config.h got included and warn or error if not
(i.e. when it would silently default to the dummy locks)
--
Ticket URL: <http://bind10.isc.org/ticket/602#comment:2>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list