From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: "24383@debbugs.gnu.org" <24383@debbugs.gnu.org>
Subject: bug#24383: [External] : Re: bug#24383: 25.1.50; Deprecation/internalization of `read-from-whole-string'
Date: Sat, 6 Feb 2021 18:52:47 +0000 [thread overview]
Message-ID: <SA2PR10MB4474C755931FD1F1A9A7F5F4F3B19@SA2PR10MB4474.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87im759xsw.fsf@gnus.org>
> > What's the rationale behind the demotion of
> > `read-from-whole-string' and its replacement by
> > "internal" function
> > `thing-at-point--read-from-whole-string'?
?
> > "This is an internal thingatpt function and should not be used."
> >
> > Should not be used? Really? Why?
>
> "Should not be used" is perhaps over-stating the case, but it's an
> internal thingatpt function with a name that didn't reflect that, so
> renaming it is appropriate.
What makes it "internal"? The name change is
based on it being internal, so the reason it's
considered internal can't be because of its name.
Does it have anything at all to do specifically
with thing-at-point? What makes it a candidate
for being designated "internal"?
Does anything in the code or the doc string
suggest thing-at-point?
"Read a Lisp expression from STR.
Signal an error if the entire string was not used."
> It's up to you whether you want to use internal
> Emacs functions, of course. Closing.
The alternative to using this function is to
reproduce its definition. Is that better?
Wouldn't it be better to move this out of
thingatpt.el? Isn't this function generally
useful?
I've copied the definition to two libraries,
unrelated to each other. That says something
about how internal this is, no?
prev parent reply other threads:[~2021-02-06 18:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 16:52 bug#24383: 25.1.50; Deprecation/internalization of `read-from-whole-string' Drew Adams
2019-11-08 3:38 ` Stefan Kangas
2021-02-06 12:37 ` Lars Ingebrigtsen
2021-02-06 18:52 ` Drew Adams [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SA2PR10MB4474C755931FD1F1A9A7F5F4F3B19@SA2PR10MB4474.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=24383@debbugs.gnu.org \
--cc=larsi@gnus.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 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.