#2409: last call for options keys consolidation ----------------------------------+----------------------------------------- Reporter: martinl | Owner: grass-dev@… Type: task | Status: new Priority: blocker | Milestone: 7.0.0 Component: Default | Version: unspecified Keywords: standardized options | Platform: Unspecified Cpu: Unspecified | ----------------------------------+-----------------------------------------
Comment(by glynn): Replying to [comment:116 wenzeslaus]: > [comment:111 annakrat] and [comment:113 hcho] don't want the underscore for 3D raster, so this changes "`raster` and (`raster_3d` and `raster3d`)" just to "`raster` and `raster3d`". [comment:102 I] already said that I prefer `raster3d` over `raster_3d`. In my opinion such a common option name as one for 3D raster (common for me and name of one of the basic types) should not have an underscore. Can someone, anyone, explain what exactly is the problem with underscores? Why are they bad, why shouldn't we use them, etc? To my mind, any name that is made of more than one word should have some kind of separator between the words. For GRASS option names, "some kind of separator" equates to an underscore. -- Ticket URL: <http://trac.osgeo.org/grass/ticket/2409#comment:121> GRASS GIS <http://grass.osgeo.org> _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev