all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: Do we need C's extern in Emacs Lisp?
Date: Thu, 31 Mar 2022 00:26:20 -0400	[thread overview]
Message-ID: <E1nZmO4-0002al-9A@fencepost.gnu.org> (raw)
In-Reply-To: <YkNF1XvLXRKSClzM@ACM> (message from Alan Mackenzie on Tue, 29 Mar 2022 17:45:57 +0000)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > Currently we do not have any equivalent in Lisp.  For example, if

  >     (defvar foo)

  > is in a Lisp file, then subsequent use of foo will generate an unknown
  > variable warning.

Could you describe the scenario more clearly?  What sort of use, and where?
The reason I ask is that details would affect whether we judge
that the actual behavior is problematical or helpful.

  > I think it would be useful to have some sort of "extern" facility in our
  > Lisp.

This raises some questions:

1. How would you envision using it?

2. What would we do currently?

3. What would be the advantage of using the new construct instead?

W
-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)





      parent reply	other threads:[~2022-03-31  4:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29 17:45 Do we need C's extern in Emacs Lisp? Alan Mackenzie
2022-03-29 21:09 ` Stefan Monnier
2022-03-31 20:59   ` Alan Mackenzie
2022-03-31 21:16     ` Stefan Monnier
2022-03-31  4:26 ` Richard Stallman [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=E1nZmO4-0002al-9A@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=acm@muc.de \
    --cc=emacs-devel@gnu.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.