Skip to content
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.

Sign up for GitHub

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

Jump to bottom

NSObject should be an abstract class #9

Closed
GoogleCodeExporter opened this issue Mar 13, 2015 · 1 comment
Closed

NSObject should be an abstract class #9

GoogleCodeExporter opened this issue Mar 13, 2015 · 1 comment
Labels
auto-migrated Priority-Critical Type-Enhancement

Comments

@GoogleCodeExporter
Copy link
Contributor 

As per the discussion on the dev mailing list, NSObject and all it's
'concrete' subclasses should be abstract classes. This allows Protocols to
be implemented as interfaces.

We need this before we can create mappings from the BridgeSupport files.

Original issue reported on code.google.com by [email protected] on 18 Oct 2009 at 10:16
@GoogleCodeExporter
Copy link
Contributor Author 

Checked in as R317

Original comment by [email protected] on 21 Oct 2009 at 3:59

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Critical Type-Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter