• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Objective C <--> COM comparison
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Objective C <--> COM comparison


  • Subject: Re: Objective C <--> COM comparison
  • From: Ondra Cada <email@hidden>
  • Date: Thu, 30 May 2002 01:52:48 +0200

On Thursday, May 30, 2002, at 01:38 , John C. Randolph wrote:

Actually, to be precise, Obj-C does have the fragile base class problem, just not as severely as C++. If you add an ivar to a class, you need to recompile any subclasses that access their inherited ivars directly.

Right, but it can be easily worked around (eg. using techniques similar to what I've just posted for class vars), entirely seamlessly, and entirely without a need to recimpile anything -- thanks to ObjC dynamicness.

There is *no* workaround for the FBC hell in C++ (but not using it and defining quite independent API, which is precisely what COM does).
---
Ondra Cada
OCSoftware: email@hidden http://www.ocs.cz
2K Development: email@hidden http://www.2kdevelopment.cz
private email@hidden http://www.ocs.cz/oc
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
References: 
 >Re: Objective C <--> COM comparison (From: "John C. Randolph" <email@hidden>)

  • Prev by Date: Re: Objective C <--> COM comparison
  • Next by Date: Re: Objective C <--> COM comparison
  • Previous by thread: Re: Objective C <--> COM comparison
  • Next by thread: Re: Objective C <--> COM comparison
  • Index(es):
    • Date
    • Thread