-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why 2 libraries (Objective-C/Swift)? #71
Comments
Historical reasons, I guess? 😅 The library started as ObjC. Then I tried to re-implement it in Swift when it was introduced. Both projects are still being used, therefore both are still being maintained. Some people want ObjC only, others Swift only, and there are good reasons for both. The sane thing would be to retire one of them, and just maintain one. I’ll probably do that at one point. PS: I’m thinking about adding a SwiftUI implementation now. Maybe just as an “add on” to the Swift version, but that’s a different discussion anyway... |
First, I think we could expose the swift framework to Objective-C. What about this? |
Using |
I don't understand why but it already works without using @objc annotations! |
Interesting. Maybe because they‘re subclasses of Objective-C classes, so there’s some inherited compatibility? But still, only the |
Exact, you are right! Ouf, because I did not understand! |
Everything that is open/public in Swift should also be accessible from Objective-C, if we want it to be fully compatible. |
I don't think so. We need to expose only the functions that a user will use in an Objective-C project. |
I understand your point of view, but some developers will want to have access to everything that is already accessible in Swift, especially if we want to retire the Objective-C library later on. |
Not an issue.
Are there any particular reasons for maintaining the two repos?
https://github.com/vtourraine/VTAcknowledgementsViewController
https://github.com/vtourraine/AcknowList
The text was updated successfully, but these errors were encountered: