unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org
Subject: Re: Trying to cope with Calendar's dynamic scoping
Date: Thu, 05 Sep 2013 13:55:15 -0400	[thread overview]
Message-ID: <h4zjrr2lx8.fsf@fencepost.gnu.org> (raw)
In-Reply-To: jwv38pj9o1y.fsf-monnier+emacs@gnu.org

Stefan Monnier wrote:

>> Was there any particular aspect you thought might not work?
>
> Well, there's the fundamental difference between lexical and dynamic
> scoping:

Oh, so nothing major then...

> While you can have
>
>    &%%(blabla date blabla)
>
> you can't have
>
>    &%%(my-cal-fun)
>
> where my-cal-fun is defined in your .emacs as
>
>    (defun my-cal-fun () (blabla date blabla))

Or defined in any third-party library. Eg it seems this would break org,
which has "helpfully" hidden the warnings from "(defvar date)".

I don't know how common such usage is.

If you think we need to move to lexical scoping for everything, then the
incompatible change has to be made at some point, it seems.
Maybe Emacs 25.1 is more appropriate for something like that?



  reply	other threads:[~2013-09-05 17:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-20 22:07 Trying to cope with Calendar's dynamic scoping Stefan Monnier
2013-08-21  0:19 ` Edward Reingold
2013-08-21  4:30   ` Stefan Monnier
2013-08-21  1:22 ` Leo Liu
2013-08-21  4:33   ` Stefan Monnier
2013-08-21  7:05 ` Glenn Morris
2013-09-05  4:58 ` Glenn Morris
2013-09-05 17:29   ` Stefan Monnier
2013-09-05 17:55     ` Glenn Morris [this message]
2013-09-05 18:59       ` Stefan Monnier
2013-09-06  1:20         ` Glenn Morris
2013-09-06 14:58           ` Stefan Monnier
2013-09-06 16:02             ` Glenn Morris
2013-09-06 17:16               ` Stefan Monnier

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=h4zjrr2lx8.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    /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).