unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: RE: server-local variables
Date: Mon, 31 Oct 2016 22:08:43 -0700 (PDT)	[thread overview]
Message-ID: <da944a7c-8a20-478f-8d2b-a38d2ff46dc0@default> (raw)
In-Reply-To: <jwv37jcvtt4.fsf-monnier+Inbox@gnu.org>

> > I use an obarray in `synonyms.el', for example, for the
> > names in a dictionary (thesaurus).
> > (https://www.emacswiki.org/emacs/Synonyms)
> 
> That's exactly an example where you use obarrays to do
> something similar to modules.

Oh, that's what you meant by "modules"?  Had you mentioned
"namespaces" (or even just separate sets of "symbols", or
even "something similar to Common Lisp packages"), that
might have been clearer.

(Especially in light of the recent discussions of adding
a different sort of "modules" to Emacs.)

See Ted's reply, where it seems he thought of an obarray
for exactly the reasons you and I apparently agree that
obarrays _can_ be appropriate: to wall off sets of symbols:

> OK, it seemed like you were basically designing a scoped
> symbol table per connection, so an obarray seemed sensible.
> I haven't worked with them so it was just a question for
> my education.  But if they are actively discouraged for
> most usage, the ELisp manual section on Creating Symbols
> should mention that.  I was not aware.

He seems to have taken your admonition somewhat similarly
to how I did.

Had you just said that you don't think separate symbol
namespaces are needed here, I don't think there would have
been any confusion.  It was not clear, to me at least, why
you said that obarray use cases are *very* rare. 

And if it _is_ needed here to have separate sets of symbols
(some of which could have the same name), then "Why not an
obarray?" isn't an unreasonable question.

Perhaps your reply was just your way of asking "Do we need
separate sets of symbols here?", or your way of saying that
we do not?



  reply	other threads:[~2016-11-01  5:08 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-30 18:39 server-local variables Michael Albinus
2016-10-30 20:08 ` Eli Zaretskii
2016-10-30 20:28   ` Michael Albinus
2016-10-31  3:30     ` Eli Zaretskii
2016-10-31  9:54       ` Michael Albinus
2016-10-31 11:17         ` Phil Sainty
2016-10-31 12:45           ` Óscar Fuentes
2016-10-31 15:42           ` Michael Albinus
2016-10-31 20:15             ` Phil Sainty
2016-10-31 13:43         ` Stefan Monnier
2016-10-31 16:30           ` Michael Albinus
2016-10-31 12:39 ` Ted Zlatanov
2016-10-31 13:36   ` Stefan Monnier
2016-10-31 21:03     ` Drew Adams
2016-11-01  2:08       ` Stefan Monnier
2016-11-01  5:08         ` Drew Adams [this message]
2016-10-31 16:26   ` Michael Albinus
2016-10-31 17:31     ` Ted Zlatanov
2016-10-31 20:47       ` Michael Albinus
2016-11-01 13:22         ` Ted Zlatanov
2016-11-14 14:02           ` Michael Albinus
2016-11-15 15:02             ` GnuTLS per-connection variables (was: server-local variables) Ted Zlatanov
2016-11-24 12:50               ` GnuTLS per-connection variables Michael Albinus
2016-11-29 16:07                 ` Ted Zlatanov
2016-11-28 18:54               ` Michael Albinus
2016-12-05 15:09                 ` Michael Albinus
2016-12-05 16:27                   ` Ted Zlatanov
2016-12-05 16:49                     ` Michael Albinus

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=da944a7c-8a20-478f-8d2b-a38d2ff46dc0@default \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).