Mercurial > emacs
changeset 70090:67a078792729
(Coding Conventions): Explain when the package's
prefix should appear later on (not at the start of the name).
| author | Richard M. Stallman <rms@gnu.org> |
|---|---|
| date | Tue, 18 Apr 2006 21:10:14 +0000 |
| parents | 3e2a72a06085 |
| children | 4427f1e01f3e |
| files | lispref/tips.texi |
| diffstat | 1 files changed, 7 insertions(+), 3 deletions(-) [+] |
line wrap: on
line diff
--- a/lispref/tips.texi Tue Apr 18 21:09:13 2006 +0000 +++ b/lispref/tips.texi Tue Apr 18 21:10:14 2006 +0000 @@ -56,9 +56,13 @@ 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