search

davekeck / Xcode-4-Fixins

Plugins for fixing Xcode 4 bugs and shortcomings
362 stars 41 forks source link

Xcode 4 support #31

Open tom-seddon opened 10 years ago

tom-seddon commented 10 years ago

At the risk of asking a stupid question... should the Xcode 4 fixins continue to support Xcode 4? :)

I've been fixing up the fixins for 5.1. Xcode 5.1 complained about the GC support, so I let it convert everything to ARC. Seems to work fine for 5.1 (I'll push the WIP branch to github in the next day or two) - but now none of them load into Xcode 4.6.2. Xcode prints a GC capability mismatch error to the console for each one.

It's annoying how quick Apple is to drop things. But since they seem to have switched to giving upgrades out for free, for OS X, Xcode, and iOS - and anybody coding for iOS is automatically committed to the Xcode treadmill - I imagine virtually everybody will upgrade.

So is continued Xcode 4 support felt to be important?

Any comments?

--Tom

andyarvanitis commented 10 years ago

I'm not an authority on it, but I'd say not to worry about 4.x support at this stage. Just my vote.

tom-seddon commented 10 years ago

That's my feeling too. It'll only become harder over time to resist the upgrade churn. I guess Apple will just drop GC entirely one day, and then nobody will be able to run Xcode 4.

I'm just going to leave this issue open for now and see if it attracts any further comment :)

Anyway, I've uploaded the Xcode 5.1 code to the xcode_51_arc branch.

--Tom

azav commented 10 years ago

Sadly, I don't think so.

tom-seddon commented 10 years ago

I plan to merge the Xcode 5 branch into master this week. There'll be a new branch based off the existing master for people who still want/need fixins for Xcode 4.6, but I doubt it will see much maintenance.

What to do about the name is still an open question ;)

--Tom

tom-seddon commented 10 years ago

Well, better late than never. Xcode 5.1 support is now on the master branch, and Xcode 4.6.2 support is on the xcode_462 branch. Yes, this means that the Xcode 4 Fixins don't support Xcode 4... suggestions welcome!

(Or can you just rename the project without it being a problem? I'd assume this would change the hashes... but maybe not?)

Next stop Xcode 6 I suppose, unless the Xcode 6 programmers have been good enough to just slavishly copy everything in the fixins :)

But I'm not doing Apple work at the moment, so I haven't looked at it.

--Tom