Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 324828 - C++ header file ending in .H are not handled properly
Summary: C++ header file ending in .H are not handled properly
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-core (show other bugs)
Version: 8.0   Edit
Hardware: PC Linux
: P3 normal with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-09 05:44 EDT by JC Berthon CLA
Modified: 2020-09-04 15:20 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description JC Berthon CLA 2010-09-09 05:44:06 EDT
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.