Component Object Model (COM) Development on Mac OS X
Subject:   Endian issues?
Date:   2004-04-21 09:10:02
From:   rufwork
What good's a COM architecture if you still have to recompile on another platform? That is, why not just keep things simple C and wrap whatever's most approrpriate for each platform instead of writing COM both places?

Let's face it, porting to the Mac is nontrivial, and using COM on the Mac won't remove the reverse of those issues to get to the PC. There are still, unf, easier ways to hit the two platforms, even with C, than COM.

Full Threads Oldest First

Showing messages 1 through 1 of 1.

  • Endian issues?
    2004-04-21 15:08:52  ChristopherHunt [View]

    Thank you for your questions rufwork.

    Using COM is not a Silver Bullet to cross-platform development. However COM *helps* you write portable software components given the methods that I describe in the article.

    COM also allows you to express interfaces in an object oriented way which you might consider an advantage over regular C interfaces.

    Endianess still has to be catered for and has nothing to do with COM.