#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:175 wenzeslaus]: > If I understand correctly, we still want to use full option names for GRASS code (and perhaps documentation) and to advise it for user scripts. Indeed. The main issues I see with abbreviations are: 1. Searching for use of an option name (grep, Ctrl+F, etc) will miss abbreviations. 2. Abbreviations make code harder to understand for people who aren't fluent in English. > In this case it would be good to have a way to proof that the full option names are used, something like an environmental variable `GRASS_FULL_OPTION_NAMES` which would switch off the advanced word/character matching and `renamed_options` so that only full names would be considered as valid. r63765 generates a warning if GRASS_FULL_OPTION_NAMES is set (to anything) and the found string isn't an exact match for the given string. -- Ticket URL: <http://trac.osgeo.org/grass/ticket/2409#comment:176> GRASS GIS <http://grass.osgeo.org> _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev