1) When in doubt, use C4! (actually, plain old dynamite should work just fine!)
2) Shoot the (idiot) developer of the C++ code for doing that (may result in
serious jail time...)
3) Fuggedabouddit!
4) Wait for ObjC 3.0 and hope it has a feature to isolate badly written (or
named) code in a namesp
On May 2, 2012, at 7:46 AM, Don Quixote de la Mancha wrote:
> Are not both Objective-C and C++, as well as Objective-C++
> case-sensitive? If so, Nil and nil should be different symbols.
They are case-sensitive. Both, "nil" and "Nil" are different macros defined for
different purposes in Obj
On May 1, 2012, at 7:16 PM, Greg Parker wrote:
> On May 1, 2012, at 7:10 AM, Andreas Grosam wrote:
>> Hm, the library is a header only template library - namely its spirit (from
>> boost), so my chances to never include this library are zero ;)
>>
>> Basically, I need something like the follow
Are not both Objective-C and C++, as well as Objective-C++
case-sensitive? If so, Nil and nil should be different symbols. If
they should be, and really are different symbols, but still conflict
somehow, then you've actually got a different problem than you think
you do.
Do Not Let The Sun Go Do
On May 1, 2012, at 7:10 AM, Andreas Grosam wrote:
> Hm, the library is a header only template library - namely its spirit (from
> boost), so my chances to never include this library are zero ;)
>
> Basically, I need something like the following to compile:
>
> // file foo.m:
>
> #include
>
>
On May 1, 2012, at 8:10 AM, Andreas Grosam wrote:
> Hm, the library is a header only template library - namely its spirit (from
> boost), so my chances to never include this library are zero ;)
I didn't say never include it; I said never include it from Objective-C++. The
fact that it is a head
On May 1, 2012, at 3:56 PM, Scott Ribe wrote:
> On May 1, 2012, at 5:44 AM, Andreas Grosam wrote:
>
>> What are my options?
>
> You might have to wrap that sucker, so that you can compile that class as
> straight C++ and never include its header from Objective-C++, but instead use
> your wrap
On May 1, 2012, at 5:44 AM, Andreas Grosam wrote:
> What are my options?
You might have to wrap that sucker, so that you can compile that class as
straight C++ and never include its header from Objective-C++, but instead use
your wrapper class from Objective-C++.
Assuming you don't want to cha
I want to use a C++ software library which uses class names "nil" and "Nil" for
a Cocoa application.
Including the headers will fail due to name conflicts with the macros "Nil" and
"nil".
What are my options?
Regards
Andreas
___
Cocoa-dev mailing l
