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

* tips.texi (Coding Conventions): Improve wording.

Browse source
This commit is contained in:
Christopher Schmidt 2013-06-26 17:22:21 +02:00
parent 23a75d7f59
commit bace801385
2 changed files with 10 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
doc/lispref/ChangeLog
View file

@ -1,3 +1,7 @@
2013-06-26 Christopher Schmidt <christopher@ch.ristopher.com>
* tips.texi (Coding Conventions): Improve wording.
2013-06-24 Glenn Morris <rgm@gnu.org>
* loading.texi (Autoload): Fix typo.

12
doc/lispref/tips.texi
View file

@ -54,12 +54,12 @@ You should choose a short word to distinguish your program from other
Lisp programs. The names of all global symbols in your program, that
is the names of variables, constants, and functions, should begin with
that chosen prefix. Separate the prefix from the rest of the name
with a hyphen, @samp{-}. Use two hyphens if the symbol is not meant
to be used by other packages. This practice helps avoid name
conflicts, since all global variables in Emacs Lisp share the same
name space, and all functions share another name space@footnote{The
benefits of a Common Lisp-style package system are considered not to
outweigh the costs.}.
with a hyphen, @samp{-}. This practice helps avoid name conflicts,
since all global variables in Emacs Lisp share the same name space,
and all functions share another name space@footnote{The benefits of a
Common Lisp-style package system are considered not to outweigh the
costs.}. Use two hyphens to separate prefix and name if the symbol is
not meant to be used by other packages.
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