• 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: returning nil on initialization
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: returning nil on initialization


  • Subject: Re: returning nil on initialization
  • From: Ondra Cada <email@hidden>
  • Date: Mon, 29 Mar 2004 21:36:46 +0200

Chaz,

On Sunday, Mar 28, 2004, at 23:13 Europe/Prague, Chaz McGarvey wrote:

So my question: is returning nil if the initialize fails generally a bad thing to do, design-wise if nothing else?

Yup, it's completely all right and up to conventions.

That, of course, does not prevent any number of programmers to ignore the conventions and write things like

-init {
[super init];
[self whatever...];
}

but *that's* completely wrong, whilst the code of yours is correct.
---
Ondra Hada
OCSoftware: email@hidden http://www.ocs.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: 
 >returning nil on initialization (From: Chaz McGarvey <email@hidden>)

  • Prev by Date: Re: Getting glyphs and their outlines
  • Next by Date: Re: NSOutlineView subclass
  • Previous by thread: returning nil on initialization
  • Next by thread: Re: returning nil on initialization
  • Index(es):
    • Date
    • Thread