Bugzilla – Full Text Bug Listing
| Summary: | C++ header file ending in .H are not handled properly | ||
|---|---|---|---|
| Product: | [Tools] CDT | Reporter: | JC Berthon <huygens_25> |
| Component: | cdt-core | Assignee: | Project Inbox <cdt-core-inbox> |
| Status: | NEW --- | QA Contact: | Jonah Graham <jonah> |
| Severity: | normal | ||
| Priority: | P3 | CC: | yevshif |
| Version: | 8.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
Build Identifier: 20100617-1415 On my current assignment, the project uses .H (uppercase H) for C++ header extension. Eclipse indexer works fine with this extension. However, the refactoring/rename feature ignores the file. Thus when you want to refactor a class name, it only performs it on the .C and ignores the .H file. I've tried to tweak the settings by adding a new file type *.H <--> C++ Header file. But Eclipse tells me that this file type already exist (which is true for *.h, the lowercase h). I've tried to even force it by creating the appropriate line in my ${workspace}/.metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.core.runtime.prefs but it is once again ignored. This bug probably is only visible on platforms which distinguish *.h from *.H at the file system level (which thus exclude FAT/NTFS). Reproducible: Always Steps to Reproduce: 1. Create a new class in an existing C++ project. 2. Name the class foo 3. Name the header with an uppercase H 4. open the header file and refactor/rename the class to foobar 5. Eclipse only applies the modification to the C++ source file, the header file is left untouched.