• 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: Bug in GCC 3.1?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bug in GCC 3.1?


  • Subject: Re: Bug in GCC 3.1?
  • From: Thomas Lachand-Robert <email@hidden>
  • Date: Tue, 7 May 2002 22:04:39 +0200

Le mardi 7 mai 2002, ` 05:35 , email@hidden a icrit :

True. And had the original code cast the variable "t" simply to "id", unadorned by any protocol declaration, I would agree that a warning would be inappropriate, because a plain old "id" can be anything.


I think you should take a little bit more time reading the complete messages. It is obvious that using a cast to id<WrongProtocol> should lead to a compiler warning, everyone does understand that. The point is that there is a warning with a cast to id, but only if the corresponding variable is declared id<SomeProtocol> and the target variable is id<SomeOtherProtocol>, and not in any other case. That exactly what I pointed out in my precendent messages (including the original one).

Thomas Lachand-Robert
********************** email@hidden
<< Et le chemin est long du projet ` la chose. >> Molihre, Tartuffe.
_______________________________________________
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: 
 >Re: Bug in GCC 3.1? (From: email@hidden)

  • Prev by Date: Re: dock menu says "Application not responding" when my app is launch ed at Startup
  • Next by Date: Re: Slighty OT: Non-Cocoa Notifications
  • Previous by thread: Re: Bug in GCC 3.1?
  • Next by thread: Cocoa Sprite Kit
  • Index(es):
    • Date
    • Thread