[Dune] [#925] Consistent Coding Style in the Core Modules (Attachment added)

[Dune]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - Andreas Lauser (andlaus) 

Attached to Project - Dune
Summary - Consistent Coding Style in the Core Modules
Task Type - Bug Report
Category - Dune Core Modules
Status - Unconfirmed
Assigned To - 
Operating System - Unspecified / All
Severity - Low
Priority - Normal
Reported Version - 2.0
Due in Version - Undecided
Due Date - Undecided
Details - Hi All,

Today I was sufficiently annoyed of the inconsistencies in the variable/typedef/constant naming that I decided to do something about it. According to

http://www.dune-project.org/doc/devel/codingstyle.html

every thing should use CamelCase and underscores are not allowed except to mark an attribute as private. In the current version of some DUNE core modules (most notably dune-common and dune-istl) the situation is quite different. The attached patch against the 2.1 branch fixes this issue for most of the dense vector/matrix stuff in dune-common by adding CamelCase names and deprecating the old names. All my code still compiles and runs without any modifications, albeit quite a few warnings appear when compiling it. I know this patch is far from complete, I just wanted to start somewhere and I want to hear a few options from actual dune developers. If it is decided that this is the way to go, I will provide complete patches for all core dune modules...  

One or more files have been attached.

More information can be found at the following URL:
http://www.dune-project.org/flyspray/index.php?do=details&task_id=925

You are receiving this message because you have requested it from the
Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.