• 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: When did forward method references become legal?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: When did forward method references become legal?


  • Subject: Re: When did forward method references become legal?
  • From: Wade Tregaskis <email@hidden>
  • Date: Tue, 06 Mar 2012 14:12:11 -0800

- (void) first { [self second]; }   // <—no longer a compile error
- (void) second { }

This gives a method not found *warning* on Xcode 4.2, OS X 10.6.8.

Yes; that's the old behaviour that's been around forever. :)

I think it might even be the case that I've been unconciously using this already, without realising it.  One of the many dangers of working in ObjC and Python simultaneously. :D

Once @import is added, things will get even more confusing (or is that simpler?).

Kudos to whomever did this in clang.  I'm too young to remember the "good old" days of anorexic C, so I welcome these improvements.
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >When did forward method references become legal? (From: Jens Alfke <email@hidden>)
 >Re: When did forward method references become legal? (From: Phillip Mills <email@hidden>)

  • Prev by Date: Dragging folders between project in X-code
  • Next by Date: Re: Xcode - AN APPLE OPPORTUNITY!
  • Previous by thread: Re: When did forward method references become legal?
  • Next by thread: Re: When did forward method references become legal?
  • Index(es):
    • Date
    • Thread