From: Philip Kaludercic <philipk@posteo.net>
To: Devon Sean McCullough <Emacs-hacker2023@jovi.net>
Cc: 72160@debbugs.gnu.org
Subject: bug#72160: 29.3; package buglet
Date: Sun, 21 Jul 2024 16:17:12 +0000 [thread overview]
Message-ID: <87jzhelnxz.fsf@posteo.net> (raw)
In-Reply-To: <e90ea5436ae5675380d768f4d91b3792@jovi.net> (Devon Sean McCullough's message of "Sun, 21 Jul 2024 10:30:32 -0500")
Devon Sean McCullough <Emacs-hacker2023@jovi.net> writes:
> On 2024-07-21 05:59, Philip Kaludercic wrote:
>> Devon Sean McCullough <Emacs-hacker2023@jovi.net> writes:
>>> Strings and symbols should be equally acceptable package designators.
>> We can improve on that error message, but is there any use-case for
>> denoting a package by a string?
>
> Consistency -- load-library takes strings.
> Features, libraries & packages all fill the same needs
> so require should take strings too.
Load-library takes a string, and signals an error if you pass it a
symbol. My take: This makes sense, since the string is denoting a file
in `load-path'. Symbols on the other hand are a kind of "protocol"
between (provide ...) and (require ...) expressions, and abstract over
loading of files, e.g. by not loading a feature that has already been
required before. Packages on the other hand are another level on top of
features, that also happens to use symbols, but with a different intent.
So to me, consistency means keeping these levels of abstraction
distinct, and not coercing inputs to match more than we do already
(e.g. with the assumption that packages always provide a feature of the
same name).
Again, what I wanted to know of there was a practical use-case for
packages to accept string; there is probably little point in discussing
matters of taste here.
> Peace
> --Devon
>
> P.S. Symbol/string dichotomy exposes implementation
> details not germane to the user's task.
>
--
Philip Kaludercic on peregrine
prev parent reply other threads:[~2024-07-21 16:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 16:16 bug#72160: 29.3; package buglet Devon Sean McCullough
[not found] ` <handler.72160.B.172123303622025.ack@debbugs.gnu.org>
2024-07-17 17:12 ` bug#72160: Acknowledgement (29.3; package buglet) Devon Sean McCullough
2024-07-18 8:59 ` bug#72160: 29.3; package buglet Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-21 10:59 ` Philip Kaludercic
2024-07-21 15:30 ` Devon Sean McCullough
2024-07-21 15:48 ` Eli Zaretskii
2024-07-21 16:17 ` Philip Kaludercic [this message]
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=87jzhelnxz.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=72160@debbugs.gnu.org \
--cc=Emacs-hacker2023@jovi.net \
/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).