[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bash prefixes
From: |
Chet Ramey |
Subject: |
Re: Bash prefixes |
Date: |
Tue, 22 Jun 2010 14:55:47 -0400 |
User-agent: |
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.7) Gecko/20100111 Lightning/1.0b1 Thunderbird/3.0.1 |
On 6/18/10 5:34 AM, Freddy Vulto wrote:
> Within the bash-completion package
> (http://bash-completion.alioth.debian.org/), we're planning on prefixing
> all functions and variables to create some kind of namespace. The
> prefixes probably are going to be:
>
> bashcomp_
> BASHCOMP_
>
> Are there any considerations to take into account regarding prefixing?
> Does bash officially "reserve" any variable/function prefix to itself?
> At least BASH_* and COMP_* seem to be used by bash.
Your choices seem fine. Bash also uses (and so, I suppose, reserves)
READLINE_*. I would use the lower-case version, since Bash restricts
itself to the uppercase ASCII character set for variable names.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/
- Bash prefixes, Freddy Vulto, 2010/06/18
- Re: Bash prefixes,
Chet Ramey <=