Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • dumux dumux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 84
    • Issues 84
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 80
    • Merge requests 80
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • dumux-repositories
  • dumuxdumux
  • Issues
  • #214

Closed
Open
Created Nov 04, 2013 by Bernd Flemisch@berndOwner

FS#214 Implement naming rules for class names

Metadata

Property Value
Project dumux
Category General
Reported by Bernd Flemisch (bernd@iws.uni-stuttgart.de)
Reported at Nov 4, 2013 09:34
Type Feature Request
Version Git
Last edited by Kilian Weishaupt (kilian.weishaupt@iws.uni-stuttgart.de)
Last edited at Jan 22, 2016 10:18

Description

From 2.3 to 2.4, all member functions and enums have been adapted to our naming conventions. We want to evaluate how we want to do this for class names. Currently, we have inconsistencies like TwoPTwoCNI and Stokes2cni. We discuss in particular the issue about digits in class names.

Newer compilers should provide easier deprecation possibilities. An example will follow.

Assignee
Assign to
Time tracking