From: Richard M. Stallman Date: Tue, 18 Apr 2006 21:10:14 +0000 (+0000) Subject: (Coding Conventions): Explain when the package's X-Git-Tag: emacs-pretest-22.0.90~3076 X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=8a1aafd01a88cda0df0873d3772487e2b0123769;p=emacs.git (Coding Conventions): Explain when the package's prefix should appear later on (not at the start of the name). --- 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