Mercurial > emacs
changeset 65344:77b6aaba307a
(Coding Conventions): Sometimes it is ok to put the
package prefix elsewhere than at the start of the name.
| author | Richard M. Stallman <rms@gnu.org> |
|---|---|
| date | Tue, 06 Sep 2005 04:40:08 +0000 |
| parents | d82393ad9b2d |
| children | 7e5239b21c5d |
| files | lispref/tips.texi |
| diffstat | 1 files changed, 3 insertions(+), 1 deletions(-) [+] |
line wrap: on
line diff
--- a/lispref/tips.texi Tue Sep 06 03:14:46 2005 +0000 +++ b/lispref/tips.texi Tue Sep 06 04:40:08 2005 +0000 @@ -56,7 +56,9 @@ benefits of a Common Lisp-style package system are considered not to outweigh the costs.} Then take care to begin the names of all global variables, constants, and functions in your program with the chosen -prefix. This helps avoid name conflicts. +prefix. This helps avoid name conflicts. (Occasionally, for a command +name intended for users to use, it is cleaner if some words come +before the package name prefix.) This recommendation applies even to names for traditional Lisp primitives that are not primitives in Emacs Lisp---such as