Commit 2a6bc1f7 authored by Richard M. Stallman's avatar Richard M. Stallman
Browse files

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

package prefix elsewhere than at the start of the name.
parent f4885d81
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
......
......@@ -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
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment