• 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: porting from codewarrior typedef chokes
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: porting from codewarrior typedef chokes


  • Subject: Re: porting from codewarrior typedef chokes
  • From: Fritz Anderson <email@hidden>
  • Date: Mon, 5 Jun 2006 13:07:26 -0500

On 5 Jun 2006, at 12:46 PM, Brian Ray wrote:

Does anybody know why this would choke gcc:
typedef void (CALLBACK LogMessageCallback)(const char*);
I get:
expected initializer before 'LogMessageCallback'

I'm not aware that CALLBACK is part of the C standard, or #defined in any header provided in the Xcode toolset. Can you use CodeWarrior to examine the definition?


	-- F

--
Fritz Anderson -- http://www.manoverboard.org/
Consulting Programmer -- http://resume.manoverboard.org/
Step into Xcode, The Ideal Flag Day Gift! -- http:// six.manoverboard.org/



_______________________________________________ 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: 
 >porting from codewarrior typedef chokes (From: "Brian Ray" <email@hidden>)

  • Prev by Date: porting from codewarrior typedef chokes
  • Next by Date: Re: Remote debugging in Xcode 2.3 on 10.2.8
  • Previous by thread: porting from codewarrior typedef chokes
  • Next by thread: adding files to Run Script build phase input files list
  • Index(es):
    • Date
    • Thread