• 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: Inconsistent Memory Management Rules
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Inconsistent Memory Management Rules


  • Subject: Re: Inconsistent Memory Management Rules
  • From: Sherm Pendley <email@hidden>
  • Date: Wed, 16 Apr 2003 01:38:06 -0400

On Tuesday, April 15, 2003, at 07:24 PM, Denis Stanton wrote:

OK, so there has to be a previous declaration. What does it look like?
In my limited knowledge I can only think it would consist of the line
NSString * string = [[NSString alloc] init]

The above combines declaration and initialization. The declaration by itself would be:

NSString *string;

The Jaguar dev tools include GCC3, which supports the C99 standard and allows you to declare variables anywhere. Older dev tools use GCC2, which requires declarations to appear at the top of a function or method, before any executable code.

sherm--

UNIX: Where /sbin/init is Job 1.
_______________________________________________
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.

  • Follow-Ups:
    • Re: Inconsistent Memory Management Rules
      • From: Denis Stanton <email@hidden>
References: 
 >Re: Inconsistent Memory Management Rules (From: Denis Stanton <email@hidden>)

  • Prev by Date: Re: "Capturing" a keyboard-like device in a Cocoa application?
  • Next by Date: Re: Newbie: Current Apps Directory
  • Previous by thread: Re: Inconsistent Memory Management Rules
  • Next by thread: Re: Inconsistent Memory Management Rules
  • Index(es):
    • Date
    • Thread