(Howard: Sorry, I hadn't meant to send that email just yet.)<br><br><div>I'm attempting to get Cinder (<a href="http://libcinder.org" target="_blank">libcinder.org</a>) to compile with libc++. It uses things like std::shared_ptr<const __CFDictionary>, which is returned const from CFDictionaryCreate(...). There's no need to modify the resulting Dictionary (and they are immutable anyway?), so it makes sense to keep the value const. Thinking "aloud," I could have a GUI element that uses a shared_ptr to reference a color from the user's preferences in order to draw itself, that the GUI element shouldn't ever modify, so the value should be const. This way, when the GUI dies, the shared_ptr does it thing and cleans up the color.</div>
<div><br></div><div>In terms of fixes, the thing that causes this is that a const type is passed into the shared_ptr. Removing the const where the shared_ptr instantiates the allocator should also fix this. Similarly the const-ness could be removed(cast/type_trait-ed) in the Cinder code, avoiding any changes to the library.</div>
<div><br></div><div>At this point, though, I'm arguing with the standard, so I lose for now. I'll get you next time, C++!</div><div><br></div><div>Thanks,</div><div>Paul O'Neil</div><div><br><div class="gmail_quote">
On Mon, Jan 2, 2012 at 1:55 AM, Paul O'Neil <span dir="ltr"><<a href="mailto:redballoon36@gmail.com">redballoon36@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
I'm attempting to get Cinder (<a href="http://libcinder.org" target="_blank">libcinder.org</a>)
to compile with libc++. It uses a std::shared_ptr<const
__CFDictionary>, which is returned from CFDictionaryCreate(...).<br>
<br>
<div class="gmail_quote"><div class="im">On Sun, Jan 1, 2012 at 10:35 PM, Howard
Hinnant <span dir="ltr"><<a href="mailto:hhinnant@apple.com" target="_blank">hhinnant@apple.com</a>></span>
wrote:<br>
</div><div><div class="h5"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The C11++ std
says that std::allocator<T> contains both of these
members:<br>
<br>
<br>
pointer address(reference x) const noexcept;<br>
const_pointer address(const_reference x) const noexcept;<br>
<br>
And when T is const, these two members result in a double
declaration of the same member. So according to the standard,
std::allocator<const T> isn't supposed to work.<br>
<br>
But let's explore beyond that.<br>
<br>
What is your use case for needing to do so? Perhaps if it is
motivating, and there is no easy workaround, libc++ could
support it as an extension.<br>
<span><font color="#888888"><br>
Howard<br>
</font></span>
<div>
<div><br>
On Jan 1, 2012, at 10:01 PM, <a href="mailto:redballoon36@gmail.com" target="_blank">redballoon36@gmail.com</a>
wrote:<br>
<br>
> Thanks for the response.<br>
><br>
> Yes, that compiles. Is there a reason that keeping the
const doesn't work? Given that you say this isn't allowed,
why is it a bad idea? The shared_ptr provided by boost
takes this.<br>
><br>
> I did some more digging in the Buzilla (I had only
searched open bugs before), and found this one: <a href="http://llvm.org/bugs/show_bug.cgi?id=8421" target="_blank">http://llvm.org/bugs/show_bug.cgi?id=8421</a>
. It looks like the same thing, but in std::map instead.
Also since emailing the list, I tried it in Visual Studio
2010 and it compiled without errors. However, I have no
idea how to work Visual Studio, so some the settings may
have been very different.<br>
><br>
> Thanks again,<br>
> Paul O'Neil<br>
><br>
> On Sun, Jan 1, 2012 at 8:12 PM, David Keller <<a href="mailto:david.keller@litchis.fr" target="_blank">david.keller@litchis.fr</a>>
wrote:<br>
> Hi,<br>
><br>
> You may write:<br>
><br>
>> std::shared_ptr<const int> ptr(new int(4));<br>
><br>
> Regards<br>
><br>
> On Dec 30, 2011, at 1:29 AM, <a href="mailto:redballoon36@gmail.com" target="_blank">redballoon36@gmail.com</a>
wrote:<br>
><br>
>> Hello,<br>
>><br>
>> I've encountered a compiler error using shared_ptr
and allocator from the libc++ header <memory>. I'm
running OS X 10.7.2, and I first noticed this while using
the libc++ implementation with Xcode 4.2.1, though I believe
this still exists in svn 147357.<br>
>><br>
>> The problem is caused by instantiating
std::allocator<> (in the memory header) with a const
type. This causes the pointer and const_pointer types to be
the same, which results in methods using these to have the
same signatures, which gives a compiler error (as it should,
given that methods are colliding). Is this supposed to
happen? I haven't read the standard, but it seems like it
should work, that is, that std::allocator<const int>
should be allowed to exist.<br>
>><br>
>> A bit of background. This gets triggered when
using:<br>
>> std::shared_ptr<const int> ptr(new const
int(4));<br>
>> which also seems like a reasonable thing to do.<br>
>><br>
>> Thanks,<br>
>> Paul O'Neil<br>
>> _______________________________________________<br>
>> cfe-dev mailing list<br>
>> <a href="mailto:cfe-dev@cs.uiuc.edu" target="_blank">cfe-dev@cs.uiuc.edu</a><br>
>> <a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev</a><br>
><br>
><br>
> _______________________________________________<br>
> cfe-dev mailing list<br>
> <a href="mailto:cfe-dev@cs.uiuc.edu" target="_blank">cfe-dev@cs.uiuc.edu</a><br>
> <a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev</a><br>
<br>
</div>
</div>
</blockquote>
</div></div></div>
<br>
<br>
</div>
</blockquote></div><br></div>