[Geany-devel] C++ file-type extensions

[Enrico Tröger]

On Wed, 8 Jul 2009 20:09:14 +0200, Enrico wrote:

>On Wed, 8 Jul 2009 16:46:59 +0200 (MEST), Yves wrote:
>
>>
>>----- original message --------
>>
>>Subject: Re: [Geany-devel] C++ file-type extensions
>>Sent: Wed, 08 Jul 2009
>>From: Frank Lanitz<frank at frank.uvena.de>
>>
>>> Am Mittwoch, den 08.07.2009, 15:18 +0200 schrieb Yves Pausch:
>>> 
>>> > As I have problems attaching the patch I provide a link instead:
>>> > http://www.ype.de/files/geany_cpp.patch
>>> 
>>> At least for .h file this would introduce wrong behaviour as header
>>> for C++ should be either .H or .hpp. Nevertheless this is something
>>> you can configure on your end. Just have a look onto
>>> http://www.geany.org/manual/current/index.html#filetype-extensions 
>>> 
>>> Cheers, 
>>> Frank 
>>
>>--- original message end ----
>>
>>The new behaviour wouldn't imho be wrong only different from the
>>existing. I don't see any drawbacks while handling C headers in the
>>same way as C++ headers apart from it isn't completely precise. Most
>>of the C++ projects that I know or I'm involved into name their
>>headers *.h and commonly only template class declarations will be put
>>into *.hpp there. Bye, Yves.
>
>And what about the other tousands of C projects around? They loose
>syntax support for their headers files by default.

One more note to clarify this a bit:
if we would set *.h as a C++ extension, opened C .h files would be
still highlighted of course even though as C++. From the highlighting
point of view this won't make much difference. But opening C header
files as C++ will affect the symbol parsing code and also
the autocompletions.
Additionally it might affect future changes in the build system (see
build-system branch in SVN).

Regards,
Enrico

-- 
Get my GPG key from http://www.uvena.de/pub.asc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.geany.org/pipermail/devel/attachments/20090709/544574c2/attachment.pgp>