unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Christopher Schmidt <christopher@ch.ristopher.com>
Cc: emacs-devel@gnu.org
Subject: Re: Naming internal functions
Date: Mon, 15 Apr 2013 17:07:24 +0300	[thread overview]
Message-ID: <83zjwz6g6b.fsf@gnu.org> (raw)
In-Reply-To: <87li8joqil@ch.ristopher.com>

> From: Christopher Schmidt <christopher@ch.ristopher.com>
> Date: Mon, 15 Apr 2013 14:46:26 +0100 (BST)
> 
> > Sounds good, tho a suggested patch would be welcome.
> 
> --- doc/lispref/tips.texi
> +++ doc/lispref/tips.texi

Thanks!

>  Lisp programs.  The names of all global variables, constants, and
>  functions in your program should begin with that chosen prefix.
>  Separate the prefix from the rest of the name 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
> +Use two hyphens if the object is not meant to be used by other
> +packages.          ^^^^^^^^^^

What "object"?  This word was never mentioned in the preceding text,
so using it here will confuse, especially those readers whose first
language is not English.  Never introduce new terminology in the
middle of a complex description, where each successive sentence builds
upon what the preceding ones said.  Always use _exactly_ the same
words as in the preceding sentences.  If you need to introduce a new
word, always describe it first.  For example:

  The names of any global objects---variables, constants, and
  functions--in your program should begin with that chosen prefix.
  Separate the prefix from the rest of the name with a hyphen, @samp{-}.
  Use two hyphens if the object is not meant to be used by other packages.

(Not that I think "objects" is good terminology in this context, but
just to show you the principle.)

> --- etc/NEWS
> +++ etc/NEWS
> @@ -409,6 +409,12 @@
>  `preserve-extended-attributes' as it now handles both SELinux context
>  and ACL entries.
>  
> +** Changes to the Emacs Lisp Coding Conventions in Emacs 24.4
> +
> +*** The package descriptor and name of global variables, constants,
> +and functions should be separated by two hypens if the object is not
> +meant to be used by other packages.

Same here.



  reply	other threads:[~2013-04-15 14:07 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08  0:23 Modern Conventions for Emacs Lisp files? Thorsten Jolitz
2013-04-08  9:32 ` Alan Mackenzie
2013-04-08 20:05   ` Thorsten Jolitz
2013-04-08 13:22 ` Stefan Monnier
2013-04-08 13:54   ` Andreas Röhler
2013-04-08 19:51     ` Thorsten Jolitz
2013-04-09  6:05       ` Andreas Röhler
2013-04-08 19:47   ` Thorsten Jolitz
2013-04-08 20:07     ` Stefan Monnier
2013-04-08 20:37       ` Thorsten Jolitz
2013-04-08 21:26         ` Stefan Monnier
2013-04-08 22:21           ` Thorsten Jolitz
2013-04-09  7:29           ` Bastien
2013-04-09 12:27             ` Stefan Monnier
2013-04-09 13:11               ` Bastien
2013-04-09 13:36                 ` Andreas Röhler
2013-04-09 13:41                   ` Bastien
2013-04-13 23:41           ` Thorsten Jolitz
2013-04-14  0:24             ` Stefan Monnier
2013-04-14  3:06             ` Stefan Monnier
2013-04-14  8:16               ` Thorsten Jolitz
2013-04-15  8:37             ` Thorsten Jolitz
2013-04-15  9:04               ` Eli Zaretskii
2013-04-15 11:16                 ` Thorsten Jolitz
2013-04-15 13:13                   ` Stefan Monnier
2013-04-15  9:09               ` Bastien
2013-04-08 20:55       ` Naming internal functions (was: Modern Conventions for Emacs Lisp files?) Christopher Schmidt
2013-04-08 21:28         ` Naming internal functions Stefan Monnier
2013-04-15 13:46           ` Christopher Schmidt
2013-04-15 14:07             ` Eli Zaretskii [this message]
2013-04-15 14:14               ` Christopher Schmidt
2013-04-15 14:25                 ` Eli Zaretskii
2013-04-15 17:08                   ` Christopher Schmidt
2013-04-15 14:16               ` xfq
2013-04-08 22:41   ` Modern Conventions for Emacs Lisp files? Pascal J. Bourguignon
2013-04-08 23:42     ` Thorsten Jolitz
2013-04-09  2:11     ` Stefan Monnier
2013-04-09  8:04       ` Thorsten Jolitz
2013-04-09 12:23         ` Stefan Monnier
2013-04-10 19:06       ` Pascal J. Bourguignon
2013-04-10 20:04         ` Thorsten Jolitz
2013-04-09  9:18 ` Leo Liu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83zjwz6g6b.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=christopher@ch.ristopher.com \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).