Le 03/05/2011 21:44, David Paleino a écrit : >> And one important thing we should be planning for is considering what is >> the bash-completion "API", i.e. what external completion authors can use >> if they like and we'll try to keep that stuff stable, and what are >> private things not intended to be used outside bash-completion proper >> and which may change/disappear pretty much anytime. I think these >> deserve different namespaces, for example __bc_* or for the private ones >> and _bc_* for the API ones, or something that makes the difference even >> more visible such as _BC_* for the API ones. (All functions that are >> used as actual top level completion functions for commands would >> probably be private.) > > I'd prefer _BC_*. I'd prefer to keep underscore prefix for private namespace only: _BC (private) vs BC (public). -- BOFH excuse #274:
It was OK before you touched it. _______________________________________________ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
