comparison lispref/tips.texi @ 38162:40606e2d6b31

Minor change.
author Richard M. Stallman <rms@gnu.org>
date Sat, 23 Jun 2001 16:10:25 +0000
parents 3577e0c41a1e
children f70837a465ac
comparison
equal deleted inserted replaced
38161:45d64a431eea 38162:40606e2d6b31
35 Here are conventions that you should follow when writing Emacs Lisp 35 Here are conventions that you should follow when writing Emacs Lisp
36 code intended for widespread use: 36 code intended for widespread use:
37 37
38 @itemize @bullet 38 @itemize @bullet
39 @item 39 @item
40 Since all global variables share the same name space, and all functions 40 Since all global variables share the same name space, and all
41 share another name space, you should choose a short word to distinguish 41 functions share another name space, you should choose a short word to
42 your program from other Lisp programs.@footnote{The benefits of a Common 42 distinguish your program from other Lisp programs.@footnote{The
43 Lisp-style package system are considered not to outweigh the costs.} 43 benefits of a Common Lisp-style package system are considered not to
44 Then take care to begin the names of all global variables, constants, 44 outweigh the costs.} Then take care to begin the names of all global
45 and functions with the chosen prefix. This helps avoid name conflicts. 45 variables, constants, and functions in your program with the chosen
46 prefix. This helps avoid name conflicts.
46 47
47 This recommendation applies even to names for traditional Lisp 48 This recommendation applies even to names for traditional Lisp
48 primitives that are not primitives in Emacs Lisp---even to 49 primitives that are not primitives in Emacs Lisp---even to
49 @code{copy-list}. Believe it or not, there is more than one plausible 50 @code{copy-list}. Believe it or not, there is more than one plausible
50 way to define @code{copy-list}. Play it safe; append your name prefix 51 way to define @code{copy-list}. Play it safe; append your name prefix