Mercurial > emacs
comparison lispref/tips.texi @ 65344:77b6aaba307a
(Coding Conventions): Sometimes it is ok to put the
package prefix elsewhere than at the start of the name.
| author | Richard M. Stallman <rms@gnu.org> |
|---|---|
| date | Tue, 06 Sep 2005 04:40:08 +0000 |
| parents | c2fb39cb93f0 |
| children | 95aa6fb80959 df78f2fb8f6a |
comparison
equal
deleted
inserted
replaced
| 65343:d82393ad9b2d | 65344:77b6aaba307a |
|---|---|
| 54 functions share another name space, you should choose a short word to | 54 functions share another name space, you should choose a short word to |
| 55 distinguish your program from other Lisp programs.@footnote{The | 55 distinguish your program from other Lisp programs.@footnote{The |
| 56 benefits of a Common Lisp-style package system are considered not to | 56 benefits of a Common Lisp-style package system are considered not to |
| 57 outweigh the costs.} Then take care to begin the names of all global | 57 outweigh the costs.} Then take care to begin the names of all global |
| 58 variables, constants, and functions in your program with the chosen | 58 variables, constants, and functions in your program with the chosen |
| 59 prefix. This helps avoid name conflicts. | 59 prefix. This helps avoid name conflicts. (Occasionally, for a command |
| 60 name intended for users to use, it is cleaner if some words come | |
| 61 before the package name prefix.) | |
| 60 | 62 |
| 61 This recommendation applies even to names for traditional Lisp | 63 This recommendation applies even to names for traditional Lisp |
| 62 primitives that are not primitives in Emacs Lisp---such as | 64 primitives that are not primitives in Emacs Lisp---such as |
| 63 @code{copy-list}. Believe it or not, there is more than one plausible | 65 @code{copy-list}. Believe it or not, there is more than one plausible |
| 64 way to define @code{copy-list}. Play it safe; append your name prefix | 66 way to define @code{copy-list}. Play it safe; append your name prefix |