Re: A CFStringRef that throws EXC_BAD_ACCESS
Re: A CFStringRef that throws EXC_BAD_ACCESS
- Subject: Re: A CFStringRef that throws EXC_BAD_ACCESS
- From: Chris Ridd <email@hidden>
- Date: Thu, 17 Oct 2002 13:55:34 +0100
On 17/10/02 11:48 am, Craig Bakalian <email@hidden> wrote:
>
But, why did the compiler let me do the first one without telling me it
>
needed a return value?
Because typically (historically?) C lets you throw away function results.
There may be a flag for gcc which warns you if you do that, though to be
honest I couldn't see one in the man pages.
Cheers,
Chris
_______________________________________________
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.