BIND 10 #2104: bare shared_ptr in static_datasrc_link.cc

[BIND 10 Development]

#2104: bare shared_ptr in static_datasrc_link.cc
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:
  fdupont                            |                Status:  new
                       Type:         |             Milestone:  Next-Sprint-
  defect                             |  Proposed
                   Priority:  high   |            Resolution:
                  Component:         |             Sensitive:  0
  Unclassified                       |           Sub-Project:  Core
                   Keywords:         |  Estimated Difficulty:  0
            Defect Severity:         |           Total Hours:  0
  Medium                             |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:4 fdupont]:

 > > Why is this „fix“ needed? There should be `using boost` at the top, so
 it should be found and I think the longer name is uglier.
 >
 > => you have (cur & paste from the file in the title):
 >
 > using namespace boost;
 > using namespace std;
 >
 > so how to choose between boost::shared_ptr and std::shared_ptr when you
 have a bare shared_ptr? In conclusion namespaces can solve conflicts only
 when they are use.
 > (BTW the source of the issue is the TR1: Microsoft implements it and
 shared_ptr is part of it)

 Just checking: so, as long as we do 'using namespace std', 'using
 boost::shared_ptr' (instead of 'using namespace boost') doesn't work
 either, right?

 Now (with C++11) the standard namespace is going to contain a lot more
 symbols, maybe we should use the same practice for 'std' as that for
 the name space boost, i.e, at least don't incorporate the entire
 namespace but be reasonably specific to avoid conflict (like 'using
 std::string').

-- 
Ticket URL: <http://bind10.isc.org/ticket/2104#comment:5>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development