From: Michael Heerdegen <michael_heerdegen@web.de>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 18059@debbugs.gnu.org, Stefan Monnier <monnier@IRO.UMontreal.CA>,
Noam Postavsky <npostavs@users.sourceforge.net>
Subject: bug#18059: 24.3.92; defvar and special variables
Date: Mon, 19 Feb 2018 02:44:23 +0100 [thread overview]
Message-ID: <87371xlpmw.fsf@web.de> (raw)
In-Reply-To: <87fu5y53w5.fsf@gmail.com> (Noam Postavsky's message of "Sun, 18 Feb 2018 17:28:26 -0500")
Noam Postavsky <npostavs@gmail.com> writes:
> This let-block thing feels more like a bug to me, so I'm inclined to
> leave it out of the manual.
Maybe somebody could clarify the rationale behind the behavior?
It would not be good to leave this undocumented - it is something people
actually do.
> I'm also not so sure about putting in examples into the manual; the
> shortest and simplest I could come up with is this, but I don't know
> that it's worth putting in.
>
> This example demonstrates the effects of using @code{defvar} without
> an initial value:
>
> @example
> @group
> (let ((x 'lexical))
> (defun get-lexical-x ()
> x))
> (defvar x)
> (defun get-dynamic-x ()
> x)
>
> (let ((x 'dynamic))
> (list (get-dynamic-x)
> (get-lexical-x)))
> @result{} (dynamic lexical)
> @end group
> @end example
Obviously I would like something like this being added.
Michael.
next prev parent reply other threads:[~2018-02-19 1:44 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-20 3:23 bug#18059: 24.3.92; defvar and special variables Michael Heerdegen
2018-02-10 19:29 ` Noam Postavsky
2018-02-10 23:59 ` Michael Heerdegen
2018-02-11 0:17 ` Drew Adams
2018-02-11 0:43 ` Noam Postavsky
2018-02-11 0:38 ` Noam Postavsky
2018-02-11 1:32 ` Michael Heerdegen
2018-02-11 2:26 ` Noam Postavsky
2018-02-11 15:14 ` Stefan Monnier
2018-02-11 15:35 ` Noam Postavsky
2018-02-11 16:38 ` Michael Heerdegen
2018-02-11 17:00 ` Noam Postavsky
2018-02-14 0:27 ` Noam Postavsky
2018-02-18 22:28 ` Noam Postavsky
2018-02-19 1:44 ` Michael Heerdegen [this message]
2018-02-21 15:09 ` Noam Postavsky
2018-02-21 16:08 ` Drew Adams
2018-02-21 16:23 ` Noam Postavsky
2018-02-21 16:33 ` Noam Postavsky
2018-02-21 17:15 ` Drew Adams
2018-02-21 18:00 ` Noam Postavsky
2018-02-21 19:14 ` Drew Adams
2018-02-21 19:19 ` Stefan Monnier
2018-02-21 22:20 ` Michael Heerdegen
2018-02-23 14:05 ` Stefan Monnier
2018-02-23 14:55 ` Michael Heerdegen
2018-03-04 23:27 ` Noam Postavsky
2018-03-05 9:51 ` Michael Heerdegen
2018-03-07 13:00 ` Noam Postavsky
2018-03-09 9:58 ` Michael Heerdegen
2018-03-09 13:43 ` Stefan Monnier
2018-03-11 16:45 ` Noam Postavsky
2018-03-11 22:16 ` Drew Adams
2018-03-14 11:15 ` Noam Postavsky
2018-03-23 12:23 ` Noam Postavsky
2018-03-05 15:57 ` Eli Zaretskii
2018-03-08 23:36 ` Noam Postavsky
2018-03-09 0:15 ` Drew Adams
2018-02-21 17:11 ` Drew Adams
2018-02-11 15:57 ` Eli Zaretskii
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=87371xlpmw.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=18059@debbugs.gnu.org \
--cc=monnier@IRO.UMontreal.CA \
--cc=npostavs@gmail.com \
--cc=npostavs@users.sourceforge.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).