• 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: Guarding against missing ObjC implementation
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Guarding against missing ObjC implementation


  • Subject: Re: Guarding against missing ObjC implementation
  • From: Daniel Jalkut <email@hidden>
  • Date: Mon, 9 Jan 2006 15:12:35 -0500

I suppose it could be argued that the disappearance of an object should itself cause some other unit test in the project to fail. I suppose I just don't have extensive enough unit testing at this point.

On Jan 9, 2006, at 12:11 PM, Daniel Jalkut wrote:

Has anybody got any clever tricks for avoiding the whole class of "dynamic functionality may carelessly disappear" problems? This particular aspect of Objective-C makes it very scary to reorganize/ refactor projects. I'm pretty-well used to the dynamic nature of the language by now, but most developers are, I think, conditioned to trust the linker to find these types of errors.

_______________________________________________ Do not post admin requests to the list. They will be ignored. Cocoa-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: Guarding against missing ObjC implementation
      • From: Daniel Jalkut <email@hidden>
References: 
 >Guarding against missing ObjC implementation (From: Daniel Jalkut <email@hidden>)

  • Prev by Date: Re: Setting values in InfoPlist.strings from Info.plist;
  • Next by Date: Re: Guarding against missing ObjC implementation
  • Previous by thread: Guarding against missing ObjC implementation
  • Next by thread: Re: Guarding against missing ObjC implementation
  • Index(es):
    • Date
    • Thread