all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Daniel Colascione <dancol@dancol.org>
To: "João Távora" <joaotavora@gmail.com>, "Vladimir Sedach" <vas@oneofus.la>
Cc: Andrea Corallo <akrl@sdf.org>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: A prototype for a binding based approach to proper namespaces
Date: Sat, 9 May 2020 17:12:14 -0700	[thread overview]
Message-ID: <a880cc8b-1e2e-ce3e-eb9d-69473f96cfb3@dancol.org> (raw)
In-Reply-To: <CALDnm53Z34qZAQOdBF5fqAE9e34W2SN-r5G1M=FuG_AT8Psdgg@mail.gmail.com>

On 5/9/20 4:53 PM, João Távora wrote:
> On Sun, May 10, 2020 at 12:30 AM Vladimir Sedach <vas@oneofus.la> wrote:
> 
>> The original motivation for the currently ongoing discussion (as I
>> understand it) is João's attempt to solve the problem of s.el
>> choosing a short prefix, without requiring all of the packages that
>> rely on s.el to change the way that they call s.el
> 
> Indeed, that is the most desired feature because there is a large
> body of programs that use s.el, f.el dash.el and such. We don't want
> the importation of one of those systems to pollute the namespace.
> Every system we idealize, whatever the approach, should keep
> its eyes on this prize, IMO.
> 
> I've personally come up with this in
> https://github.com/joaotavora/elisp-shorthand
> so you can add it to the 7 or so I've counted so far.
> 
> Vlamidir, earlier you had many questions about the shorthand
> approach that I couldn't answer.  shorthand.el is less than 50 loc,
> it's reasonably easy to read.  It's very dumb, and doesn't do
> any fancy stuff, but it does solve the problem.  Obviously, a proper
> implementation wouldn't use advice, but proper interfaces.

Another problem with prefix-less imports is the semantic confusion. Lots 
of symbols are named such that their function is clear only in context 
of the package to which they belong. For example, tramp has 
tramp-syntax-values, tramp-prefix-format-alist, tramp-prefix-regexp, and 
tramp-error. Importing these symbols as just syntax-values, 
prefix-format-alist, prefix-regexp, and error and using them without 
further qualification would probably lead to confusion at reference 
sites. "Uh... prefix-regexp? Prefix of what? Where? Huh?"

If these symbols were instead imported as t:syntax-values, 
t:prefix-format-alist, t:prefix-regexp, and t:error, reference sites 
would be almost as clear as they are now (because the reader would ask 
himself "what does t: stand for?") while being much more terse.



  reply	other threads:[~2020-05-10  0:12 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-08 20:47 A prototype for a binding based approach to proper namespaces Andrea Corallo
2020-05-08 23:43 ` Daniel Colascione
2020-05-09  8:05   ` Andrea Corallo
2020-05-09 15:16     ` Daniel Colascione
2020-05-09 15:50       ` Andrea Corallo
2020-05-09 15:56         ` Daniel Colascione
2020-05-09 16:39           ` Andrea Corallo
2020-05-09 16:41             ` Daniel Colascione
2020-05-09 17:15               ` Andrea Corallo
2020-05-09 17:17                 ` Daniel Colascione
2020-05-09 23:14                   ` Andrea Corallo
2020-05-09 23:46                     ` João Távora
2020-05-09 23:29     ` Vladimir Sedach
2020-05-09 23:53       ` João Távora
2020-05-10  0:12         ` Daniel Colascione [this message]
2020-05-10  4:18         ` Vladimir Sedach
2020-05-10 15:24       ` Andrea Corallo
2020-05-10 17:46         ` Vladimir Sedach
2020-05-10 20:14           ` Andrea Corallo
2020-05-09  7:38 ` Helmut Eller
2020-05-09  8:27   ` Andrea Corallo
2020-05-09  8:50     ` Helmut Eller
2020-05-09 10:57       ` Andrea Corallo
2020-05-09 16:09   ` Dmitry Gutov
2020-05-09 18:08     ` Helmut Eller
2020-05-09 18:55       ` Dmitry Gutov
2020-05-09 22:52 ` Vladimir Sedach

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

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

  git send-email \
    --in-reply-to=a880cc8b-1e2e-ce3e-eb9d-69473f96cfb3@dancol.org \
    --to=dancol@dancol.org \
    --cc=akrl@sdf.org \
    --cc=emacs-devel@gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=vas@oneofus.la \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.