[Bash-completion-devel] Namespace

[David Paleino]

On Wed, 04 May 2011 09:33:07 +0200, Guillaume Rousse wrote:

> 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).

That would pollute B<TAB>, as Ville wrote before. Granted, uppercase commands
are rare in the *nix world, but I can't tell for others (Darwin? *BSD?)

-- 
 . ''`.   Debian developer | http://wiki.debian.org/DavidPaleino
 : :'  : Linuxer #334216 --|-- http://www.hanskalabs.net/
 `. `'`  GPG: 1392B174 ----|---- http://deb.li/dapal
   `-   2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/bash-completion-devel/attachments/20110504/c647dbca/attachment.pgp>