• 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: Initializing NSError **, again Re: CoreData Migration Problems
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Initializing NSError **, again Re: CoreData Migration Problems


  • Subject: Re: Initializing NSError **, again Re: CoreData Migration Problems
  • From: Scott Anguish <email@hidden>
  • Date: Wed, 9 Feb 2011 14:04:09 -0500

If you pass &blah, if there is no error, blah == nil

Perhaps by-reference would be a better terminology.

Returns, by-reference, an NSError object if the regex is invalid; otherwise nil. Pass nil if you don't care.

Would that be preferable to folks?

Sent from my iPhone

On Feb 9, 2011, at 1:51 PM, Matt Neuburg <email@hidden> wrote:

>
>> Date: Tue, 8 Feb 2011 17:07:00 -0600
>> From: Fritz Anderson <email@hidden>
>> Subject: Initializing NSError **, again Re: CoreData Migration
>>    Problems
>>
>> I'm filing a bug against the documentation because it's flat wrong; or if it's right, it's a workaround for a bug, and the variance from universal practice has to be flagged conspicuously, not just casually mentioned.
>
> Howsabout this one, from NSRegularExpression:
>
>> + (NSRegularExpression *)regularExpressionWithPattern:(NSString *)patternoptions:(NSRegularExpressionOptions)options error:(NSError **)error
>> ...
>
>> error
>> An out value that returns any error encountered during initialization. Returns nil if the regular expression pattern is invalid.
>
> Really? :) m.
>
> --
> matt neuburg, phd = email@hidden, http://www.tidbits.com/matt/
> pantes anthropoi tou eidenai oregontai phusei
> Among the 2007 MacTech Top 25, http://tinyurl.com/2rh4pf
> AppleScript: the Definitive Guide, 2nd edition
> http://www.tidbits.com/matt/default.html#applescriptthings
> Take Control of Exploring & Customizing Snow Leopard
> http://tinyurl.com/kufyy8
> RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html
> TidBITS, Mac news and reviews since 1990, http://www.tidbits.com
>
>
> _______________________________________________
>
> Cocoa-dev mailing list (email@hidden)
>
> 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:
>
> This email sent to email@hidden
_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Initializing NSError **, again Re: CoreData Migration Problems
      • From: Wim Lewis <email@hidden>
References: 
 >Initializing NSError **, again Re: CoreData Migration Problems (From: Matt Neuburg <email@hidden>)

  • Prev by Date: Re: Get ProcessSerialNumber of last front application
  • Next by Date: Re: Get ProcessSerialNumber of last front application
  • Previous by thread: Initializing NSError **, again Re: CoreData Migration Problems
  • Next by thread: Re: Initializing NSError **, again Re: CoreData Migration Problems
  • Index(es):
    • Date
    • Thread