Article:		BYOB: Build Your Own Browser, Part 2
Subject:		Compile warnings expected?
Date:		2004-05-30 06:46:20
From:		jamie_young
Good article, I appreciate the move into a bit more advanced topics with actual code. It seems that advanced cocoa articles are getting hard to find, especially ones done after XCode was released. All that said, I wish the advanced articles could be a bit longer with more details covering the advanced topics. I really don't mind reading articles that span more than 3 web pages. (It seems many of the O'Reilly articles I find are targeted for a max of 3-4 pages). Anyway, on to my question: I am getting 4 compile warnings and was wondering if they are expected or if I have an elusive typo in my code somewhere. Still being new to Cocoa, I am not sure when 'Warnings' are ok and when they should actually be ignored. ;) /.../MyDocument.m: In function `-[MyDocument connectURL:]': /.../MyDocument.m:68: warning: `WebFrame' may not respond to `-loadRequest:' /.../MyDocument.m:68: warning: cannot find method `-loadRequest:'; return type `id' assumed /.../MyDocument.m: In function `-[MyDocument webView:createWebViewWithRequest:]': /.../MyDocument.m:81: warning: `WebFrame' may not respond to `-loadRequest:' /.../MyDocument.m:81: warning: cannot find method `-loadRequest:'; return type `id' assumed Thanks! ~jamie

Showing messages 1 through 4 of 4.

• re: Compile warnings expected?
  2004-05-30 07:50:03  Andrew Anderson | [View]
  
  
  Jamie,
  Glad you like the article. Good news is that a third part of the article is already in the hands of the editor and going to be published next friday, so that should make up for some of the article length.
  
  As for your warnings, as a rule it is ok but not advisable to ignore warnings that come from XCode/GCC. Warnings come when the compiler (GCC in the default existance) is confused about something, but nothing is actually wrong with the code. They often happen because the code calls a method within in a class that GCC can't identify.
  
  In this instance Objective C gets these warnings because "WebFrame.h" has not been included, so it can not determine if "loadRequest" is one of WebFrame's methods. You can ignore this because "loadRequest" is one of WebFrame's methods, but if you want it to go away add "#import <WebKit/WebView.h>" to "MyDocument.h".
  
  Andrew
  
  
  
• re: Compile warnings expected?
  2004-05-31 17:23:38  johnts [View]
  
  
  Nice article, always looking for more Cocoa tutorials.
  
  I was also getting the warnings, and adding an #import did fix it, however I added "#import <WebKit/WebFrame.h>" Now I get another warning:
  
  

  /Users/john/desktop/NewBrowser/MyDocument.m:102: warning: `WebDataSource' may not respond to `-request'

  
  
  I'm guessing it's just another import.
• re: Compile warnings expected?
  2004-05-31 17:32:24  Andrew Anderson | [View]
  
  
  could be. if you give me the actual code that is on line 102 (or 100-105 or so) of your MyDocument.m, I can get more of an idea of what is happening...
• re: Compile warnings expected?
  2004-06-01 06:07:02  johnts [View]
  
  
  I'm not at my Mac, but I believe it was this line:
  
NSString *url = [[[[frame provisionalDataSource]
request] URL]
absoluteString];

  
  I got rid of the warning by adding "#import <WebKit/WebDataSource.h>