Re: gcc poison, how to catch use of strcpy()?
Re: gcc poison, how to catch use of strcpy()?
- Subject: Re: gcc poison, how to catch use of strcpy()?
- From: "Sean McBride" <email@hidden>
- Date: Tue, 19 May 2009 15:37:26 -0400
- Organization: Rogue Research Inc.
On 5/19/09 11:27 AM, Shawn Erickson said:
>> Is your suggestion to hack the system headers to add the deprecated
>> decoration? I guess that would work.
>
>No not really was just pointing out that Apple does mark things
>deprecated (and how they do it) since you implied they don't by your
>limited statement.
I guess I could have been clearer; I am aware of gcc's deprecation facility.
>If folks find things that should be marked
>deprecated file defects about it so the next rev. of the SDK gets
>improved.
Naturally. I filed <rdar://problem/5287653> for strcpy() specifically,
but it 'behaves correctly' (no doubt because it is part of the std C
lib, but anyway...
Still, I seek a solution for today. :)
Thanks for the other ideas/comments.
>/me hopes the static analyzer in clang would pickup these types of
>basic checks (if it doesn't already do it)
It does not. I forget if I filed a bug with them too...
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden