• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: compiler bug?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: compiler bug?


  • Subject: Re: compiler bug?
  • From: Robert Tillyard <email@hidden>
  • Date: Sat, 22 Mar 2003 12:39:55 +0000

Shouldn't that be time (&now);

Regards, Rob.

On Saturday, March 22, 2003, at 06:55 am, Frank Fenn wrote:

Hi all,

this is a weird problem.

I've a method: - (IBAction)doDomething:(id)sender where I get the current time with now = time(0); now is of type time_t;
In another method for the same class -(void)doSomethingElse the use of current = time(0); generates the following error
message: called object is not a function

I had to write a normal C-function: time_t getTime() { return time(0); } and call this in "doSomethingElse". Is this a compiler
bug or do I miss something here?

--

regards
Frank Fenn - Bright Light Software
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

References: 
 >compiler bug? (From: Frank Fenn <email@hidden>)

  • Prev by Date: Window resize by blob, not by resize corner
  • Next by Date: Re: object instance names generated on the fly?
  • Previous by thread: compiler bug?
  • Next by thread: Maintaining *one* singleton over >1 thread
  • Index(es):
    • Date
    • Thread