Re: [boost] [Inspect] More Apple issues

Subject: Re: [boost] [Inspect] More Apple issues
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2010-05-06 06:39:13

Rene Rivera wrote:
> On 5/5/2010 12:44 PM, Stewart, Robert wrote:
> > John Maddock wrote:
> >>
> >> I keep getting bug reports from users who want to compile code as
> >> Objective-C++ in order to use the Apple OS X headers...
> >> unfortunately this adds some more relatively common names that we
> >> can't use
> >> (<http://developer.apple.com/mac/library/documentation/cocoa/conceptual/ObjectiveC/Articles/ocCPlusPlus.html#//apple_ref/doc/uid/TP30001163-CH10-TPXREF167>):
> >>
> >> id, Class, SEL, IMP, and BOOL
> >
> > Are these new names or is this just a new request?  I'm thinking it
> > would be nice if we could push the source of those names to avoid
> > injecting such common names into the global namespace.  If it's
> > simply part of the Objective-C++ language, then I guess we're stuck.
>
> They are types and defines in Apple Objective C runtime
> headers which are often used in conjunction with not just
> Objective C++, but also with plain C++ if you are
> interfacing with Objective C objects in some form (For
> example I have a minimal equivalent of BPL for Objective
> C). As for pushing Apple for using such common symbols..
> good luck with that ;-)

If they aren't presently aware of the effect, they might be made more sensitive to such names in the future.  It doesn't hurt to try, does it?

_____
Rob Stewart                           robert.stewart_at_[hidden]
Software Engineer, Core Software      using std::disclaimer;
Susquehanna International Group, LLP  http://www.sig.com

IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.