From kdevelop-bugs  Fri May 27 13:24:41 2005
From: kdevelop-bugs-admin () barney ! cs ! uni-potsdam ! de
Date: Fri, 27 May 2005 13:24:41 +0000
To: kdevelop-bugs
Subject: [Bug 106379] New: Support for extensionless filenames for source
Message-Id: <20050527152439.106379.hattons () globalsymmetry ! com>
X-MARC-Message: https://marc.info/?l=kdevelop-bugs&m=118306937307178

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=106379         
           Summary: Support for extensionless filenames for source
           Product: kdevelop
           Version: CVS
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: hattons globalsymmetry com


Version:           CVS (using KDE 3.4.0 Level "b" , SUSE 9.2 UNSUPPORTED)
Compiler:          gcc version 3.3.4 (pre 3.3.5 20040809)
OS:                Linux (i686) release 2.6.8-24.14-default

This is related to #94710, but it's different enough to justify a new bug report. I'm working with OpenSceneGraph.  The toolkit is very nice in many ways. One decision the core developers made which has proven very problematic for me is to use header files without extensions on the filenames.  Instead they chose to identify their files using the Emacs style mode specification -*-c++-*- in the first line of the files.  Take a look at the includes to see what I mean:

http://www.openscenegraph.org/documentation/OpenSceneGraph/include/

This causes problems with KDevelop in a few ways.  PCS cannot be used to build a code completion database.  When one of these header files is opened, it is treated like a normal text file.  There is no syntax highlighting, and none of the other language support features work. Header files with extensionless file names also cannot be created with KDevelop.  That is currently not much of a problem for me because I am not directly adding code to the cvs.  But if I were to want to contribute my own code there would be problems using KDevelop to do so.  

It's really quite easy to scan a directory for files with the mode specification line.  
for f in $(grep -lr '\-*-c++-*-' *);do echo "#include <$f>"; done > all.hpp
will create a file #including all the header files in the include path of the project.  Perhaps one approach to some of these issues might be to create a list of files intended to be treated as headers, and pass that list to such tools as PCS.  

I really don't like the extensionless headers, but the lead developer on the OSG project certainly believes the problem is with my tools and not his file names.