TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

ObjC equivalents to Swift solutions #1: Avoiding ObjC class name collisions

12 点作者 penpapersw大约 8 年前

3 条评论

jordansmithnz大约 8 年前
A few days ago I downloaded a third party iOS library, written in Obj-C. It was provided as part of a paid cloud API service. After integrating it, I was amazed (horrified?) to find that the whole library had been implemented without class prefixes. There were multiple collisions with Swift classes in my project.<p>Surprisingly the app still compiled, but tried to use the library class definitions instead of my own. I didn&#x27;t end up using the library, or continuing with the API service.
评论 #14118084 未加载
andymatuschak大约 8 年前
Historically, one of the key dangers with using unprefixed names has been that future system updates <i>add</i> new classes which collide. Testing at dev-time won&#x27;t future-proof you very well.
评论 #14118195 未加载
评论 #14117954 未加载
评论 #14117633 未加载
ruleabidinguser大约 8 年前
It doesn&#x27;t seem very forward thinking to start a <i>new app</i> in whats essentially a deprecated language.
评论 #14117842 未加载
评论 #14117579 未加载
评论 #14117733 未加载
评论 #14118025 未加载
评论 #14118218 未加载