procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

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

Browse source 
package prefix elsewhere than at the start of the name.
This commit is contained in:
Richard M. Stallman 2005-09-06 04:40:23 +00:00
parent f4885d8137
commit 2a6bc1f7ca
2 changed files with 8 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
lispref/ChangeLog
View file

@ -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

4
lispref/tips.texi
View file

@ -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