Quick follow-up for anyone interested...

On Sep 8, 2015, at 5:45 PM, has <hengist.p...@virgin.net <mailto:hengist.p...@virgin.net>> wrote: I will need to spend some more time building it out and testing it, but (touch-wood) it looks like the problem might be cracked at last. Wahey!

So, my first attempt to replace all my base classes with protocol extensions failed fairly quickly: trying to move instance vars and non-convenience inits into protocol extensions is a recipe for madness.

However, my second attempt, where I retain the main base classes and move only the 'factory' vars/methods to protocol extensions did eventually yield successful (if slightly convoluted and confusing) results:

    https://bitbucket.org/hhas/swiftae/

Next up, trying to wrangle the inconsistencies and aggravations of Swift's object/non-object and type systems into something that actually works right. Wish my teeth luck - with the amount of enamel left, they will need it. :p

Thanks again,

has

_______________________________________________

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to