5 ms·
Is Swift 4 not yet stable? The point is, I couldn't even migrate from Swift 4 to the latest with my current M1 MacBook. (You need old XCode to migrate from 4.0
by nevster 5y ago
Is Swift 4 not yet stable? The point is, I couldn't even migrate from Swift 4 to the latest with my current M1 MacBook. (You need old XCode to migrate from 4.0 to 4.2) What's surprising is the very quick dropping of the migration tools from Xcode.
- bee_rider 5y agoOut of curiosity (I mostly use old languages so I'm definitely missing something), why does migrating require support from Xcode? It's just text, right? I mean fundamentally you could just copy the files over and then fix them to be compatible with the changes in the language, right? (Does Xcode have some automagic tool to convert between different version of the language?)
- nevster 5y agoTechnically, yes. In the easiest cases it's just changes in library function names so effectively the migration tool is just handling all that search and replace for you. Of course there's more complex stuff than that. There's also all the ancillary build files and project setting files that get updated. All pretty tedious to investigate and do by hand, especially for someone like me who just wants to get their old app running again on the latest iOS.
- bee_rider 5y agoPretty annoying that they'd pull the rug like that. Actually, kinda worse than the bad-old way of doing things. I'm sure if they hadn't set the expectation that such a tool would exist, you'd have set your code up to be more easily search/replaced (or sprinkle macros around, etc).
- nicoburns 5y ago> Out of curiosity (I mostly use old languages so I'm definitely missing something), why does migrating require support from Xcode? That's just Apple being Apple unfortunately.