Xcode should not offer to import .m files in autocompletion

Originator:pburleson
Number:rdar://11489450 Date Originated:19-May-2012 12:32 AM
Status:Duplicate (9535451) Resolved:
Product:Developer Tools Product Version:4.3.2 (4E2002)
Classification:Enhancement Reproducible:Always
 
Summary:

Xcode should not offer to import .m files in the autocompletion for #import statements. 

Steps to Reproduce:

1. Create a project

2. Create a new class called Foo

3. Create a new class called Bar

4. In Bar.h type #import "Foo

Expected Results:

The only choice given to autocomplete is Foo.h

Actual Results:

Both Foo.h and Foo.m are offered. 

Notes:

The odds of needing to #import a .m file are close to nil. Offering them all the time is just confusing and can lead to compilation errors if completion is done quickly and the .m file is the file chosen.

Comments

+1

By paul at May 20, 2012, 3:48 a.m. (reply...)

+1

By dewindj at May 19, 2012, 1:43 p.m. (reply...)

Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!