Re: CopyCStringToPascal
Re: CopyCStringToPascal
- Subject: Re: CopyCStringToPascal
- From: Jon Guyer <email@hidden>
- Date: Thu, 16 Jun 2005 14:46:08 -0400
On Jun 16, 2005, at 2:23 PM, Markus Hitter wrote:
Am 16.06.2005 um 18:07 schrieb Bryan Pietrzak:
I was so pleased to see Apple add these APIs years ago so every
project I worked on didn't have it own stupid set of string
converters. Now we'll all be right back where we were because people
will be afraid to use a "deprecated" API. Ugh.
How else would you attempt to get rid of outdated stuff?
How about some explanation of what "deprecated" means, in a particular
instance[*]? How about "This API won't go away until the last Pascal
API is removed from the ToolBox"? Then, if people want to use
CopyCStringToPascal for their own nefarious purposes, they've had fair
warning, and nobody else needs to worry about it because it won't go
away on them while they still need to call it to talk to system APIs.
[*] Yes, I realize that this could lead to shear lunacy, like actually
defining what's meant by "thread safe". Since nobody wants that,
perhaps it's best to leave the headers in their present inscrutable
state.
_______________________________________________
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