(Coding Conventions): Sometimes it is ok to put the

package prefix elsewhere than at the start of the name.

diff --git a/lispref/ChangeLog b/lispref/ChangeLog
index ec8885138b5c4bcf71b9efa1f6b81c0915e11e62..8fc5754bf80eb3a68daccde25b00c53788748f95 100644 (file)
--- a/lispref/ChangeLog
+++ b/lispref/ChangeLog
@@ -1,3 +1,8 @@
+2005-09-06  Richard M. Stallman  <rms@gnu.org>
+
+       * tips.texi (Coding Conventions): Sometimes it is ok to put the
+       package prefix elsewhere than at the start of the name.
+
 2005-09-03  Richard M. Stallman  <rms@gnu.org>
 
        * tips.texi (Programming Tips): Add conventions for minibuffer

diff --git a/lispref/tips.texi b/lispref/tips.texi
index d651eb95f0efeadedabb646316cba80676175c85..fbf18047bde3f5f84150eb97bbd77cb15f7281f5 100644 (file)
--- a/lispref/tips.texi
+++ b/lispref/tips.texi
@@ -56,7 +56,9 @@ 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.
+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