BIND 10 #2332: define and implement wrapper interface for conditional variables
BIND 10 Development
do-not-reply at isc.org
Tue Oct 9 16:20:39 UTC 2012
#2332: define and implement wrapper interface for conditional variables
-------------------------------------+-------------------------------------
Reporter: | Owner:
jinmei | Status: new
Type: task | Milestone:
Priority: | Sprint-20121023
medium | Resolution:
Component: | Sensitive: 0
b10-auth | Sub-Project: DNS
Keywords: | Estimated Difficulty: 5
Defect Severity: N/A | Total Hours: 0
Feature Depending on Ticket: |
background zone loading |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by jinmei):
Replying to [comment:3 vorner]:
> I've seen different opinions on friend declarations, some saying it is
wrong
> the same way as goto is wrong (which is questionable at best as well).
The
> other side says that a well-used friend declaration can keep you public
> interface clean and simple while still allowing cooperation of related
classes.
> I somewhat agree with the second group and I think this is exactly the
case. I
> think the code I posted looks reasonably readable.
I don't necessarily disagree with that. My main point is that we
should learn from existing practices like boost thread, instead of
only thinking about what we just come up with as a given constraint.
On top of understanding how others design such stuff, considering
their pros and cons and whether we can use any of existing techniques,
if the decision is still to use the introduction of things like friend
to our current classes, I'm okay with that.
--
Ticket URL: <http://bind10.isc.org/ticket/2332#comment:5>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list