From 2a6bc1f7cae62b2ddfdf574ba4686fdecb92bfc7 Mon Sep 17 00:00:00 2001 From: "Richard M. Stallman" Date: Tue, 6 Sep 2005 04:40:23 +0000 Subject: [PATCH] (Coding Conventions): Sometimes it is ok to put the package prefix elsewhere than at the start of the name. --- lispref/ChangeLog | 5 +++++ lispref/tips.texi | 4 +++- 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/lispref/ChangeLog b/lispref/ChangeLog index ec8885138b5..8fc5754bf80 100644 --- a/lispref/ChangeLog +++ b/lispref/ChangeLog @@ -1,3 +1,8 @@ +2005-09-06 Richard M. Stallman + + * 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 * tips.texi (Programming Tips): Add conventions for minibuffer diff --git a/lispref/tips.texi b/lispref/tips.texi index d651eb95f0e..fbf18047bde 100644 --- a/lispref/tips.texi +++ b/lispref/tips.texi @@ -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 -- 2.39.2