Ah, we can easily go to the loony bin with this one. You have to start doing:

typedef struct Foo
{
Byte a;
} Foo;

#ifdef __cplusplus
class Bar
{
private:
Foo     mFoo;
};
#endif

or just refactor your code and (in this case) add a ProjectTypes.h
which contains common structures and types (common to all 3 languages:
 C++, Obj-C, C).

But remember, we got to this state because we tried to do a retro fit
(aka kludge).  Do a proper MVC (Model, View, Controller) and you can
have a C++ data model ("back end") with a
Cocoa/PowerPlant/MFC/Whatever front end.  Hell, wrap the data model
with Obj-C if you want.

(also discussed to death in the archives).

Cheers,
-H.

On 03/04/2008, Scott Ribe <[EMAIL PROTECTED]> wrote:
> > #ifdef __cplusplus
>  >
>  > C++ stuff
>  >
>  > #endif
>
>
> As long as you don't need to reference the C++ stuff from a .m file. But
>  then, should the header even be included by any .m files? Sure, there are
>  times when C++ and non-C++ stuff might belong together in a header, but most
>  of the time my C++ headers are all C++...
>
>
>  --
>  Scott Ribe
>  [EMAIL PROTECTED]
>  http://www.killerbytes.com/
>  (303) 722-0567 voice
>
>
>
>  _______________________________________________
>
>  Cocoa-dev mailing list ([email protected])
>
>  Please do not post admin requests or moderator comments to the list.
>  Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
>  Help/Unsubscribe/Update your Subscription:
>
> http://lists.apple.com/mailman/options/cocoa-dev/bogvardi%40gmail.com
>
>  This email sent to [EMAIL PROTECTED]
>
_______________________________________________

Cocoa-dev mailing list ([email protected])

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to [EMAIL PROTECTED]

Reply via email to