Re: CopyCStringToPascal
Re: CopyCStringToPascal
- Subject: Re: CopyCStringToPascal
- From: Markus Hitter <email@hidden>
- Date: Fri, 17 Jun 2005 09:43:01 +0200
Am 16.06.2005 um 21:57 schrieb Bryan Pietrzak:
On Jun 16, 2005, at 2:44 PM, Markus Hitter wrote:
Let me rephrase: How would you stop using people functions like
this in new code, how would you encourage them to eventually
replace their code with more modern APIs
Easily... new APIs use CFStringRefs.
This doesn't answer my question. Mac OS X and it's API's have a
redundancy of well over 60% (my estimate) already and I appreciate it
very much Apple starts to phase out the really old stuff. The world
is moving on and nothing worse than crippled new implementations
because you have to honor stuff which is outdated for over 10 years.
and how would you justify maintenance costs due to added
complexity in API, (Apple's) code and compiler?
This can't seriously be a concern for some Pascal and C string
utility functions which were written once ages ago and are just
handful of tens of thousands of Mac OS X APIs.
It can, because not removing them stops Apple from removing other
things, like gcc's pascal string kludge for example.
Many third party developers costs to reimplement these yet again.
Retest them.
If they reimplement them instead of modernizing their vintage code, I
can't help. Importers for old data can be done without them.
Just to prove some Unicode point?
To free developers using modern API's and users using modern apps
from the burden of obsolete functionality. Code complexity, memory
footprint, maintenance costs, library sizes ... you name it.
Markus
- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/
_______________________________________________
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