all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Payas Relekar <relekarpayas@gmail.com>,
	"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : CL packages landed
Date: Fri, 21 Oct 2022 20:13:57 +0000	[thread overview]
Message-ID: <SJ0PR10MB54884160F187D2976F1C372DF32D9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87k04t6vv3.fsf@gmail.com>

> >> I've pushed the branch "pkg" which implements CL packages for Emacs.
> >
> > Bonne initiative !  Really appreciated, Gerd.
> > ___
> >
> > Now we should figure out a good way to disambiguate
> > the use of the word "package", for our docs etc.,
> > to help users understand that this and the Emacs
> > "package" system are completely different species.
> 
> Elixir has 'module' and I quite like it, but that might conflict with so
> called 'dynamic modules' in Emacs land.

Dunno whether you see that as a possibility for the
existing "package" system or as a possibility for
CL "packages".  Could be either.

CL packages are essentially _namespaces_ - something
less than what modules are sometimes asked to do.

(FWIW, I think it's too bad we chose "package" for a
library, but it is what it is.)  We could perhaps
choose "namespace" for what's really (or essentially?)
a CL package.



  reply	other threads:[~2022-10-21 20:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21 15:24 [External] : CL packages landed Payas Relekar
2022-10-21 20:13 ` Drew Adams [this message]
2022-10-23 19:11   ` No to CL packages Richard Stallman
2022-10-24  4:40     ` Gerd Möllmann
2022-10-28 21:59       ` Richard Stallman
2022-10-29  5:18         ` Gerd Möllmann
  -- strict thread matches above, loose matches on Subject: below --
2022-10-21  4:47 CL packages landed Gerd Möllmann
2022-10-21 15:06 ` [External] : " Drew Adams
2022-10-21 17:21   ` Gerd Möllmann
2022-10-21 20:13     ` Drew Adams

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=SJ0PR10MB54884160F187D2976F1C372DF32D9@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=relekarpayas@gmail.com \
    /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.