# HG changeset patch
# User Richard M. Stallman <rms@gnu.org>
# Date 1145394614 0
# Node ID 67a078792729814c37a5af3885a3f0d64905ffa3
# Parent  3e2a72a06085c3ab23fc44d65cd4381a23fd7b26
(Coding Conventions): Explain when the package's
prefix should appear later on (not at the start of the name).

diff -r 3e2a72a06085 -r 67a078792729 lispref/tips.texi
--- 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