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

  • SEARCH
  • Home
  • 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 8401493
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 9, 20262026-06-09T21:49:15+00:00 2026-06-09T21:49:15+00:00

I have this in my interface: @property (nonatomic, weak) NSTimeInterval *timeStamp; Which my logic

  • 0

I have this in my interface:

@property (nonatomic, weak) NSTimeInterval *timeStamp;

Which my logic told me, I need a time stamp object, that only is going to be used by this class within the context of its instantiation, so “weak” seemed to be logical to me– but XCode tells me “property with ‘weak’ attribute must be of object type”… If I just do:

@property (nonatomic) NSTimeInterval *timeStamp;

Then the error goes away, but I am not sure I understand why…

  • 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-06-09T21:49:17+00:00Added an answer on June 9, 2026 at 9:49 pm

    The problem is that NSTimeInterval is a value type — it’s an alias for double, essentially (check NSDate.h for the typedef). The weak attribute only applies to objects that have a retain count (that is, anything that descends from NSObject or NSProxy).

    As such, storing a pointer to NSTimeInterval is probably a mistake on your part. You will most likely never receive a pointer to an NSTimeInterval unless you’re expected to write to a given address as an output to a function (probably a callback in such a case). That said, I’m not aware of any functions with NSTimeInterval * as a return type nor any that pass the same to a callback.

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

Sidebar

Related Questions

I have this header: @interface MyBusinessesController : UIViewController @property (weak, nonatomic) IBOutlet UITableView *businessList;
So I have a view controller which adopts UITableViewDelegate: @interface MyViewController:UIViewController<UITableViewDelegate> @property (weak, nonatomic)
Say I have this Class @interface CustomClass : NSObject @property (nonatomic, strong) NSArray *
I have this interface: public interface IValidationCRUD { public ICRUDValidation IsValid(object obj); private void
I have this JUnit test that I need help developing a Interface and Class
I have this code (which is way simplified from the real code): public interface
Under ARC , I have an object, Child that has a weak property, parent
I have a class with a property which is a weak reference to a
I have: @interface A @property (nonatomic, retain) B *toB; @end @interface B @property (nonatomic,
I have this situation: interface MessageListener { void onMessageReceipt(Message message); } class MessageReceiver {

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.