diff options
author | Richard M. Stallman <rms@gnu.org> | 2006-04-18 21:10:14 +0000 |
---|---|---|
committer | Richard M. Stallman <rms@gnu.org> | 2006-04-18 21:10:14 +0000 |
commit | aec319437c33417570a8df3c80d149218604517f (patch) | |
tree | c37a9335681f6f2675cfab1a13ddc7c38fc4d7c4 /lispref | |
parent | a2548d5d7c7ec9d652ae8230b6450861de0ccba0 (diff) | |
download | emacs-aec319437c33417570a8df3c80d149218604517f.tar.gz |
(Coding Conventions): Explain when the package's
prefix should appear later on (not at the start of the name).
Diffstat (limited to 'lispref')
-rw-r--r-- | lispref/tips.texi | 10 |
1 files changed, 7 insertions, 3 deletions
diff --git a/lispref/tips.texi b/lispref/tips.texi index 8b033139275..889ac3e6a6d 100644 --- a/lispref/tips.texi +++ b/lispref/tips.texi @@ -56,9 +56,13 @@ distinguish your program from other Lisp programs.@footnote{The 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. (Occasionally, for a command -name intended for users to use, it is cleaner if some words come -before the package name prefix.) +prefix. This helps avoid name conflicts. + +Occasionally, for a command name intended for users to use, it is more +convenient if some words come before the package's name prefix. And +constructs that define functions, variables, etc., work better if they +start with @samp{defun} or @samp{defvar}, so put the name prefix later +on in the name. This recommendation applies even to names for traditional Lisp primitives that are not primitives in Emacs Lisp---such as |