Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 1066975
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 16, 20262026-05-16T20:05:29+00:00 2026-05-16T20:05:29+00:00

I am porting a project from C# to Objective-C, and I would like to

  • 0

I am porting a project from C# to Objective-C, and I would like to know how to implement an Internal class in Objective-C (Internal meaning only visible inside of this project).

For example, I have the code in C#:

public abstract class AbstractBaseClass : AInterface
{
     // methods go here
}

internal class InternalSubclass : AbstractBaseClass
{
     // methods go here
}

This Is the code I have converted so far:

// AbstractBaseClass.h
#import <Foundation/Foundation.h>
#import "AInterface.h"

@interface AbstractBaseClass : NSObject<AInterface>

// methods go here

@end

// AbstractBaseClass.m
#import "AbstractBaseClass.h"

@implementation AbstractBaseClass

-(void) abstractMethod
{
      [NSException raise:@"abstract method" format:@"This method is abstract, and thus cannot be called"];
}

// more methods

@end

Where should I put the interfaces and implementations of InternalSubclasses? Should they be in a separate file called InternalClasses.h/m? Or should I just not have a header for those files and just have a .m file for them.

Any help would be appreciated!

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-16T20:05:30+00:00Added an answer on May 16, 2026 at 8:05 pm

    Thank you for all your answers, I have decided to make the classes public, as I will be the only one using this library at this time. I was really just wondering if I had missed something in the documentation of the Objective C language about internal classes, because you can mark variables as @package.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

No related questions found

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.