POV-Ray : Newsgroups : povray.unofficial.patches : Got Boost and VC10 "ambiguous shared_ptr"?...heres why : Re: Got Boost and VC10 "ambiguous shared_ptr"?...heres why Server Time
6 Dec 2023 19:13:18 EST (-0500)
  Re: Got Boost and VC10 "ambiguous shared_ptr"?...heres why  
From: Warp
Date: 21 Oct 2011 17:21:25
Message: <4ea1e254@news.povray.org>
Thorsten Froehlich <tho### [at] trfde> wrote:
> On 21.10.11 21:34, [GDS|Entropy] wrote:
> >  From microsoft connect:
> > http://connect.microsoft.com/VisualStudio/feedback/details/522404/share-ptr

> It is actually sufficient to use a boost version aware of the TR1 
> implementation of your library or to disable the TR1 / C++11 support in your 
> library.

>  > Explicitly state: boost::shared_ptr

> That is a kludge, not a solution.

  Because disabling support for the C++ *standard* in the compiler isn't
a kludge. Right.

  (Your position might have had more weight when shared_ptr was only part
of the TR1 extension but not yet part of the C++ standard. However, now
that it is part of the official standard, your argument is just bogus.)

  I'm sorry to say this, and not to disrespect your competence as a C++
programmer, but your stubborness with regard to the language is detrimental.
Explicit namespace qualifications in names are not "kludges". They are not
only a completely normal and standard way of programming, they are actually
the *recommended* way of programming C++ (for the precise reason to avoid
name collisions). If anything, it's the "using namespace" feature that's a
kludge, which got introduced to the first C++ standard mainly for
compatibility with pre-standard compilers (although it does have some uses
in some cases, which do not include dumping an entire namespace into the
global namespace).

                                                          - Warp

Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.